From: Krzysztof Kozlowski Date: Sat, 2 Apr 2022 10:07:06 +0000 (+0200) Subject: Documentation/process: mention patch changelog in review process X-Git-Tag: v6.1-rc5~1172^2~74 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0c603a5c704fcfead5e85e4c89c297d2be68b671;p=platform%2Fkernel%2Flinux-starfive.git 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 Signed-off-by: Jonathan Corbet --- diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index fb496b2..9bb4e8c 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.