Documentation/process: mention patch changelog in review process

Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

kernel os linux

Extend the "Respond to review comments" section of "Submitting patches"
with reference to patch changelogs.

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Krzysztof Kozlowski and committed by

Jonathan Corbet 4 years ago 0c603a5c 31231092

+4 -1

1 changed file

expand all

Documentation

process

submitting-patches.rst

+4 -1

Documentation/process/submitting-patches.rst

··· 318 318 Be sure to tell the reviewers what changes you are making and to thank them 319 319 for their time. Code review is a tiring and time-consuming process, and 320 320 reviewers sometimes get grumpy. Even in that case, though, respond 321 - politely and address the problems they have pointed out. 321 + politely and address the problems they have pointed out. When sending a next 322 + version, add a ``patch changelog`` to the cover letter or to individual patches 323 + explaining difference aganst previous submission (see 324 + :ref:`the_canonical_patch_format`). 322 325 323 326 See Documentation/process/email-clients.rst for recommendations on email 324 327 clients and mailing list etiquette.