diff options
| author | Krzysztof Kozlowski | 2022-04-02 12:07:06 +0200 |
|---|---|---|
| committer | Jonathan Corbet | 2022-04-05 09:15:29 -0600 |
| commit | 0c603a5c704fcfead5e85e4c89c297d2be68b671 (patch) | |
| tree | 61c797aadd7126cfbbe162ffc14396fb7bf9c350 /Documentation/process | |
| parent | 3123109284176b1532874591f7c81f3837bbdc17 (diff) | |
Documentation/process: mention patch changelog in review process
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>
Diffstat (limited to 'Documentation/process')
| -rw-r--r-- | Documentation/process/submitting-patches.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index fb496b2ebfd3..9bb4e8c0f635 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -318,7 +318,10 @@ understands what is going on. Be sure to tell the reviewers what changes you are making and to thank them for their time. Code review is a tiring and time-consuming process, and reviewers sometimes get grumpy. Even in that case, though, respond -politely and address the problems they have pointed out. +politely and address the problems they have pointed out. When sending a next +version, add a ``patch changelog`` to the cover letter or to individual patches +explaining difference aganst previous submission (see +:ref:`the_canonical_patch_format`). See Documentation/process/email-clients.rst for recommendations on email clients and mailing list etiquette. |