workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker.ct@bp.renesas.com>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	stable@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH v2 2/2] docs: stable-kernel-rules: remind reader about DCO
Date: Mon, 17 Jun 2024 14:18:05 +0100	[thread overview]
Message-ID: <c20a8d7c-a732-4425-ad8c-c5998ed8977e@bp.renesas.com> (raw)
In-Reply-To: <20240615020356.5595-2-shung-hsi.yu@suse.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2280 bytes --]

On 15/06/2024 03:03, Shung-Hsi Yu wrote:
> When sending patch authored by someone else to stable, it is quite easy for the
> sender to forget adding the Developer's Certification of Origin (DCO, i.e.
> Signed-off-by). An example of such can be seen in the link below. Mention DCO
> explicitly so senders are less likely to forget to do so and cause another
> round-trip.
> 
> Add a label in submitting-patches.rst so we can directly link to the DCO
> section.
> 
> Link: https://lore.kernel.org/stable/2024051500-underage-unfixed-5d28@gregkh/
> Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
> ---
> Change from v1:
> - explicitly refer to the link as an example in the 1st paragraph (Paul)
> - commit message typo fix s/explicilty/explicitly/ (Paul)
> ---
>  Documentation/process/stable-kernel-rules.rst | 4 ++++
>  Documentation/process/submitting-patches.rst  | 1 +
>  2 files changed, 5 insertions(+)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index d22aa2280f6e..85a91fd40da9 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -168,6 +168,10 @@ If the submitted patch deviates from the original upstream patch (for example
>  because it had to be adjusted for the older API), this must be very clearly
>  documented and justified in the patch description.
>  
> +Be sure to also include a :ref:`Developer's Certificate of Origin
> +<sign_your_work>` (i.e. ``Signed-off-by``) when sending patches that you did
> +not author yourself.
> +
>  
>  Following the submission
>  ------------------------
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 66029999b587..98f1c8d8b429 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -394,6 +394,7 @@ e-mail discussions.
>  
>  ``git send-email`` will do this for you automatically.
>  
> +.. _sign_your_work:
>  
>  Sign your work - the Developer's Certificate of Origin
>  ------------------------------------------------------

Reviewed-by: Paul Barker <paul.barker.ct@bp.renesas.com>

-- 
Paul Barker

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3577 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      reply	other threads:[~2024-06-17 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15  2:03 [PATCH v2 1/2] docs: stable-kernel-rules: provide example of specifing target series Shung-Hsi Yu
2024-06-15  2:03 ` [PATCH v2 2/2] docs: stable-kernel-rules: remind reader about DCO Shung-Hsi Yu
2024-06-17 13:18   ` Paul Barker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c20a8d7c-a732-4425-ad8c-c5998ed8977e@bp.renesas.com \
    --to=paul.barker.ct@bp.renesas.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=shung-hsi.yu@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).