mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sasha Levin <sashal@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Bradley Morgan <brads@mainlining.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v4] docs: submitting-patches: say which commit a Fixes tag names
Date: Mon, 02 Nov 2026 09:24:34 -0700	[thread overview]
Message-ID: <87cxsncibh.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261020142534.3533478-1-sashal@kernel.org>

Sasha Levin <sashal@kernel.org> writes:

> The description of the Fixes: tag does not say which commit to name when
> a later commit made an older bug reachable, or when more than one commit
> introduced the same bug, and both questions come up regularly. The
> commit that blame points at is also often one that only moved the code.
>
> Say that the tag names the commit that introduced the bug, that a
> later commit that exposed it gets a tag too, as handling-regressions.rst
> already asks for the commit causing a regression, and that each commit
> that introduced the bug separately gets its own tag. Say that the tags
> tell the stable team which trees need the fix, and that trees without
> any of the tagged commits do not.
>
> Link: https://lore.kernel.org/r/c3ce794d-1ac2-4ef3-9e5c-1e171bd77a89@leemhuis.info
> Link: https://lore.kernel.org/r/20261013003535-mutt-send-email-mst@kernel.org
> Link: https://lore.kernel.org/r/atCI4q2HvqVXOag1@stanley.mountain
> Link: https://lore.kernel.org/r/bcef59f8-33fe-4bbe-8429-307630dc6bb5@leemhuis.info
> Assisted-by: LLM
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
> v4:
>  - Split out of the agents skills series, where this was patch 2/7 of v3:
>    https://lore.kernel.org/r/20261016152828.3765695-3-sashal@kernel.org
>  - Take Thorsten's rewording. A later commit that exposed the bug now
>    gets a Fixes: tag too, as handling-regressions.rst already asks.
>
>  Documentation/process/submitting-patches.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)

Applied, thanks.

jon

      parent reply	other threads:[~2026-11-02 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 14:25 Sasha Levin
2026-10-25 14:21 ` Daniel Pereira
2026-11-02 16:24 ` Jonathan Corbet [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=87cxsncibh.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=brads@mainlining.org \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mst@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®