aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/process
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2023-07-06 22:15:38 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2023-07-06 22:15:38 -0700
commit7210de3a328c4df5cb8b25b2ef5703c72d8842e9 (patch)
treebf949740baf326de009e6d9df02ddf693b7f410a /Documentation/process
parent1793eac148d0136f9afe877766b9d8f4458fbf21 (diff)
parente27cb89a22ada4e3e7bee1567a8daa1fb2260b78 (diff)
downloadlinux-7210de3a328c4df5cb8b25b2ef5703c72d8842e9.tar.gz
Merge tag 'docs-6.5-2' of git://git.lwn.net/linux
Pull mode documentation updates from Jonathan Corbet: "A half-dozen late arriving docs patches. They are mostly fixes, but we also have a kernel-doc tweak for enums and the long-overdue removal of the outdated and redundant patch-submission comments at the top of the MAINTAINERS file" * tag 'docs-6.5-2' of git://git.lwn.net/linux: scripts: kernel-doc: support private / public marking for enums Documentation: KVM: SEV: add a missing backtick Documentation: ACPI: fix typo in ssdt-overlays.rst Fix documentation of panic_on_warn docs: remove the tips on how to submit patches from MAINTAINERS docs: fix typo in zh_TW and zh_CN translation
Diffstat (limited to 'Documentation/process')
-rw-r--r--Documentation/process/6.Followthrough.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/process/6.Followthrough.rst b/Documentation/process/6.Followthrough.rst
index a173cd5f93d284..66fa400c6d9405 100644
--- a/Documentation/process/6.Followthrough.rst
+++ b/Documentation/process/6.Followthrough.rst
@@ -51,6 +51,13 @@ mind:
working toward the creation of the best kernel they can; they are not
trying to create discomfort for their employers' competitors.
+ - Be prepared for seemingly silly requests for coding style changes
+ and requests to factor out some of your code to shared parts of
+ the kernel. One job the maintainers do is to keep things looking
+ the same. Sometimes this means that the clever hack in your driver
+ to get around a problem actually needs to become a generalized
+ kernel feature ready for next time.
+
What all of this comes down to is that, when reviewers send you comments,
you need to pay attention to the technical observations that they are
making. Do not let their form of expression or your own pride keep that