Debian Patches
Status for thunderbolt-tools/0.9.3-7
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Add-CODEOWNERS-file-for-automatic-review-assignment.patch | [PATCH 1/8] Add CODEOWNERS file for automatic review assignment | Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-03-23 | ||
| 0002-tests-Fix-build-errors-in-docker-environment.patch | [PATCH 2/8] tests: Fix build errors in docker environment At the moment building of umockdev is failing but we do not need it since all needed changes were incorporated upstream and packaged at least for debian/testing. This saves us time building umockdev in the container out of sources. |
Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-03-23 | ||
| 0003-tbtadm-check-sysfs-device-file-for-thunderbolt-devic.patch | [PATCH 3/8] tbtadm: check sysfs device file for thunderbolt device first. Exception like below doesn't looks nice, catch early |
Nirmoy Das <ndas@suse.de> | no | 2018-03-14 | ||
| 0004-tbtadm-Remove-boost-make_iterator_range.patch | [PATCH 4/8] tbtadm: Remove boost::make_iterator_range Replace boost:make_iterator_range with simpler construction |
Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-03-28 | ||
| 0005-tbtadm-Implement-trim-without-boost-library.patch | [PATCH 5/8] tbtadm: Implement trim without boost library Implement right trim since we need to trim ending newline characters only. |
Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-03-29 | ||
| 0006-tbtadm-Remove-boost-header-includes.patch | [PATCH 6/8] tbtadm: Remove boost header includes | Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-03-29 | ||
| 0007-tbtadm-Simplify-directory-check.patch | [PATCH 7/8] tbtadm: Simplify directory check Make code cleaner and make it possible to switch to std::filesystem. |
Andrei Emeltchenko <andrei.emeltchenko@intel.com> | no | 2018-04-03 | ||
| 0008-Make-tbtacl-safer-to-use-with-untrusted-input-63.patch | [PATCH 8/8] Make tbtacl safer to use with untrusted input (#63) This is mostly just the result of running shellcheck and following its advice. |
Benjamin Staffin <benley@gmail.com> | no | 2018-07-02 |