28 lines
1.6 KiB
Markdown
28 lines
1.6 KiB
Markdown
[ type description here; PLEASE REMOVE THIS LINE AND THE LINES BELOW BEFORE SUBMITTING THIS PULL REQUEST ]
|
|
|
|
<!--
|
|
* Although we *occasionally* also accept GitHub pull requests, the *preferred* way is sending patches to our mailing list: https://lore.kernel.org/ltp/
|
|
There is an example how to use it: https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial#7-submitting-the-test-for-review (using git format-patch and git send-email).
|
|
LTP mailing list is archived at: https://lore.kernel.org/ltp/.
|
|
We also have a patchwork instance: https://patchwork.ozlabs.org/project/ltp/list/.
|
|
|
|
* Commits should be signed: Signed-off-by: Your Name <me@example.org>, see
|
|
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
|
|
|
|
* Commit message should be meaningful, following common style
|
|
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#split-changes
|
|
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
|
|
https://cbea.ms/git-commit/
|
|
|
|
* New code should follow Linux kernel coding style, see
|
|
https://www.kernel.org/doc/html/latest/process/coding-style.html.
|
|
You can run 'make check' or 'make check-foo' in the folder with modified code to check style and common errors.
|
|
|
|
* For more tips check
|
|
https://github.com/linux-test-project/ltp/wiki/Maintainer-Patch-Review-Checklist
|
|
https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
|
|
https://github.com/linux-test-project/ltp/wiki/C-Test-API
|
|
https://github.com/linux-test-project/ltp/wiki/Shell-Test-API
|
|
https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial
|
|
-->
|