From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Sasha Levin <sashal@kernel.org>,
workflows@vger.kernel.org, ksummit@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mark Brown <broonie@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Leon Romanovsky <leon@kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Kees Cook <kees@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Dan Carpenter <error27@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Julia Lawall <julia.lawall@inria.fr>, SJ Park <sj@kernel.org>,
Bradley Morgan <brads@mainlining.org>
Subject: Re: [PATCH v4 3/5] agents: add a skill to determine stable tags
Date: Wed, 21 Oct 2026 09:55:48 +0200 [thread overview]
Message-ID: <2026102130-hazing-amusing-990a@gregkh> (raw)
In-Reply-To: <abe59717-d93c-411b-821c-b6fd24965960@leemhuis.info>
On Wed, Oct 21, 2026 at 08:56:24AM +0200, Thorsten Leemhuis wrote:
> On 10/20/26 18:16, Sasha Levin wrote:
> > Whether a fix needs a stable tag, and which releases it should reach, is
> > decided by hand and is often missed or left too broad. Add a skill that
> > [...]
>
> Thx for this!
>
> > +
> > +Judge a change by what it does, not by how its description labels it: a
> > +"cleanup" that releases a resource on an error path fixes a leak. In practice,
> > +the stable trees take:
> > +
>
> Shouldn't something like "It fixes a user-reported regression" be in
> here -- maybe even at the top of the list given that "no regressions" is
> our #1 rule?
Sure, that would be nice too, an add-on-patch for it perhaps?
thanks,
greg k-h
next prev parent reply other threads:[~2026-10-21 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 16:16 [PATCH v4 0/5] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages Sasha Levin
2026-10-20 16:16 ` [PATCH v4 1/5] agents: add infrastructure for agent resources Sasha Levin
2026-10-20 16:16 ` [PATCH v4 2/5] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-20 16:16 ` [PATCH v4 3/5] agents: add a skill to determine stable tags Sasha Levin
2026-10-21 6:45 ` Greg Kroah-Hartman
2026-10-21 6:56 ` Thorsten Leemhuis
2026-10-21 7:55 ` Greg Kroah-Hartman [this message]
2026-10-20 16:16 ` [PATCH v4 4/5] agents: add a skill to find other instances of a fixed bug Sasha Levin
2026-10-20 16:16 ` [PATCH v4 5/5] agents: add a skill to write commit messages Sasha Levin
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=2026102130-hazing-amusing-990a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=brads@mainlining.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=error27@gmail.com \
--cc=geert@linux-m68k.org \
--cc=julia.lawall@inria.fr \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mst@redhat.com \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tytso@mit.edu \
--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