From: Shung-Hsi Yu <shung-hsi.yu@suse.com>
To: Paul Barker <paul.barker.ct@bp.renesas.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
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 2/2] docs: stable-kernel-rules: remind reader about DCO
Date: Sat, 15 Jun 2024 09:57:29 +0800 [thread overview]
Message-ID: <x7nuehxxk3cn3ra46abw3y5jks2h4ikwzc6iv7cmxw7sexla37@efgriowgekfa> (raw)
In-Reply-To: <0f7d5012-99a3-485a-b500-1d79d69a64f9@bp.renesas.com>
On Thu, Jun 06, 2024 at 09:21:39AM GMT, Paul Barker wrote:
> On 06/06/2024 07:43, 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). Mention DCO explicilty so senders are less likely to
>
> s/explicilty/explicitly/
>
> > 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/
>
> Is "Link:" right here? I'd prefer to see something like "For example see
> ..." added to the first paragraph so it's explicit that this is a link
> to an example of this issue.
Thanks for the feedback. Yes that is better. Will clarify that, fix
typo, and slighly edit patch 1 as suggested.
Shung-Hsi
next prev parent reply other threads:[~2024-06-15 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 6:43 [PATCH 1/2] docs: stable-kernel-rules: provide example of specifying target series Shung-Hsi Yu
2024-06-06 6:43 ` [PATCH 2/2] docs: stable-kernel-rules: remind reader about DCO Shung-Hsi Yu
2024-06-06 8:21 ` Paul Barker
2024-06-15 1:57 ` Shung-Hsi Yu [this message]
2024-06-06 8:14 ` [PATCH 1/2] docs: stable-kernel-rules: provide example of specifying target series Paul Barker
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=x7nuehxxk3cn3ra46abw3y5jks2h4ikwzc6iv7cmxw7sexla37@efgriowgekfa \
--to=shung-hsi.yu@suse.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.barker.ct@bp.renesas.com \
--cc=sashal@kernel.org \
--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