mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
<!--
|
|
The RIOT community cares a lot about code quality.
|
|
Therefore, before describing what your contribution is about, we would like
|
|
you to make sure that your modifications are compliant with the RIOT
|
|
coding conventions, see https://github.com/RIOT-OS/RIOT/blob/master/CODING_CONVENTIONS.md.
|
|
-->
|
|
|
|
### Contribution description
|
|
|
|
<!--
|
|
Put here the description of your contribution:
|
|
- describe which part(s) of RIOT is (are) involved
|
|
- if it's a bug fix, describe the bug that it solves and how it is solved
|
|
- you can also give more information to reviewers about how to test your changes
|
|
-->
|
|
|
|
|
|
### Testing procedure
|
|
|
|
<!--
|
|
Details steps to test your contribution:
|
|
- which test/example to compile for which board and is there a 'test' command
|
|
- how to know that it was not working/available in master
|
|
- the expected success test output
|
|
-->
|
|
|
|
|
|
### Issues/PRs references
|
|
|
|
<!--
|
|
Examples: Fixes #1234. See also #5678. Depends on PR #9876.
|
|
|
|
Please use keywords (e.g., fixes, resolve) with the links to the issues you
|
|
resolved, this way they will be automatically closed when your pull request
|
|
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
|
|
-->
|