1[ type description here; PLEASE REMOVE THIS LINE AND THE LINES BELOW BEFORE SUBMITTING THIS PULL REQUEST ] 2 3<!-- 4* Although we *occasionally* also accept GitHub pull requests, the *preferred* way is sending patches to our mailing list: https://lore.kernel.org/ltp/ 5There 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). 6LTP mailing list is archived at: https://lore.kernel.org/ltp/. 7We also have a patchwork instance: https://patchwork.ozlabs.org/project/ltp/list/. 8 9* Commits should be signed: Signed-off-by: Your Name <me@example.org>, see 10https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin 11 12* Commit message should be meaningful, following common style 13https://www.kernel.org/doc/html/latest/process/submitting-patches.html#split-changes 14https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes 15https://cbea.ms/git-commit/ 16 17* New code should follow Linux kernel coding style, see 18https://www.kernel.org/doc/html/latest/process/coding-style.html. 19You can run 'make check' or 'make check-foo' in the folder with modified code to check style and common errors. 20 21* For more tips check 22https://github.com/linux-test-project/ltp/wiki/Maintainer-Patch-Review-Checklist 23https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines 24https://github.com/linux-test-project/ltp/wiki/C-Test-API 25https://github.com/linux-test-project/ltp/wiki/Shell-Test-API 26https://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial 27--> 28