mirror of https://github.com/torvalds/linux.git
aeb218d900
The purpose of this section is to document what is the current practice regarding clean-up patches which address checkpatch warnings and similar problems. I feel there is a value in having this documented so others can easily refer to it. Clearly this topic is subjective. And to some extent the current practice discourages a wider range of patches than is described here. But I feel it is best to start somewhere, with the most well established part of the current practice. Signed-off-by: Simon Horman <horms@kernel.org> Link: https://patch.msgid.link/20241009-doc-mc-clean-v2-1-e637b665fa81@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org> |
||
|---|---|---|
| .. | ||
| 1.Intro.rst | ||
| 2.Process.rst | ||
| 3.Early-stage.rst | ||
| 4.Coding.rst | ||
| 5.Posting.rst | ||
| 6.Followthrough.rst | ||
| 7.AdvancedTopics.rst | ||
| 8.Conclusion.rst | ||
| adding-syscalls.rst | ||
| applying-patches.rst | ||
| backporting.rst | ||
| botching-up-ioctls.rst | ||
| changes.rst | ||
| code-of-conduct-interpretation.rst | ||
| code-of-conduct.rst | ||
| coding-style.rst | ||
| contribution-maturity-model.rst | ||
| cve.rst | ||
| deprecated.rst | ||
| development-process.rst | ||
| email-clients.rst | ||
| embargoed-hardware-issues.rst | ||
| handling-regressions.rst | ||
| howto.rst | ||
| index.rst | ||
| kernel-docs.rst | ||
| kernel-driver-statement.rst | ||
| kernel-enforcement-statement.rst | ||
| license-rules.rst | ||
| maintainer-handbooks.rst | ||
| maintainer-kvm-x86.rst | ||
| maintainer-netdev.rst | ||
| maintainer-pgp-guide.rst | ||
| maintainer-soc-clean-dts.rst | ||
| maintainer-soc.rst | ||
| maintainer-tip.rst | ||
| maintainers.rst | ||
| management-style.rst | ||
| programming-language.rst | ||
| researcher-guidelines.rst | ||
| security-bugs.rst | ||
| stable-api-nonsense.rst | ||
| stable-kernel-rules.rst | ||
| submit-checklist.rst | ||
| submitting-patches.rst | ||
| volatile-considered-harmful.rst | ||