The contents of the usb directory were moved to appropriate locations and the usb directory removed.
* Public USB headers moved under drivers/
* Internal USB headers moved under drivers/internal/
* USB Source code moved under drivers/source/usb/
* Moved usb/device/hal/ under hal/usb/
* Moved usb/device/USBPhy/ under hal/usb/
* Merged usb/device/targets/ into targets/
* Separated public and private USB API documentation under Doxygen groups drivers-public-api and drivers-internal-api.
Separate drivers, events, and rtos internal APIs from public APIs.
* Move source files to source subdirs
* Move internal headers to internal subdirs
* Add Doxygen comments for documenting internal and public APIs
* Remove source code from header files in order to remove include pre-processor directives
that included header files not directly used by said header files
* Explicitly include header files instead of implicit inclusions via third-party header files.
Release Notes
This will break user code that was using an internal API as the internal header files have been moved.
This will only break if the user was including the header file using a namespace (i.e #include "foo/bar.h" instead of #include "bar.h"
Primary cause of false Travis CI failures was running 'apt-get update'.
Refactored all instances where this was needed with manually fetching and installing dependencies in S3 instace.
This also includes GCC installation.
Swapped out 'git grep' for 'grep' since it can take in a --max-count flag.
The license _header_ will always be at the top.
Also enabled output so that PR authors can know what the problem files are.
Consolidated efforts from PR #9336.
Previous job's env vars would not be populated correctly if the base branch of a PR was not master.
Corected by pulling remaining respository information to perform comparison between read-only instance of PR and base branch.
Fix comes from rabbitmq:
> On December 1st, 2018 (GMT) all repositories under the RabbitMQ account on PackageCloud
will be switched to use the new signing keys. RabbitMQ users who install packages
from PackageCloud must import the new signing keys before the migration.
The recommended way of doing that is by re-running PackageCloud setup
scripts (RabbitMQ, Erlang). Signing keys can be downloaded and imported directly
as well (RabbitMQ, Erlang). If the new keys are not imported, package installation
will start failing with a signature verification error.
George Psimenos
Hugues Kamba
Qinghao Shi
Cruz Monrreal II
Cruz Monrreal II
Oren Cohen
Russ Butler
Michael Schwarcz
Martin Kojtal
Aleksi Klasila
kegilbert
Oren Cohen
Olli-Pekka Puolitaival
Teppo Järvelin