From: Sasha Levin <sashal@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: broonie@kernel.org, corbet@lwn.net, error27@gmail.com,
geert@linux-m68k.org, gregkh@linuxfoundation.org,
kees@kernel.org, konstantin@linuxfoundation.org,
ksummit@lists.linux.dev, laurent.pinchart@ideasonboard.com,
leon@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@leemhuis.info,
mst@redhat.com, rdunlap@infradead.org, skhan@linuxfoundation.org,
stable@vger.kernel.org, tytso@mit.edu, workflows@vger.kernel.org
Subject: Re: [PATCH v3 0/7] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages
Date: Tue, 20 Oct 2026 09:31:56 -0400 [thread overview]
Message-ID: <20261020133156.3153106-1-sashal@kernel.org> (raw)
In-Reply-To: <20261016160030.118973-1-ojeda@kernel.org>
On Fri, Oct 16, 2026 at 06:00:30PM +0200, Miguel Ojeda wrote:
>If we are going to have a skill for the stable bit and you are updating
>the list, then may we take the chance to include Rust soundness issue?
>Please see below.
Could you send it as a separate patch to Greg and stable@? It doesn't really
depend on this series.
3/7 only drops rules that LLMs follow more strictly than the stable trees
actually apply them. Adding a new kind of fix to the list is a policy
change, and it should get its own review rather than ride along here.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-20 13:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:28 [PATCH v3 0/7] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages Sasha Levin
2026-10-16 15:28 ` [PATCH v3 1/7] agents: add infrastructure for agent resources Sasha Levin
2026-10-16 16:02 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin
2026-10-16 15:28 ` [PATCH v3 2/7] docs: submitting-patches: say which commit a Fixes tag names Sasha Levin
2026-10-16 16:03 ` Bradley Morgan
2026-10-17 8:07 ` Thorsten Leemhuis
2026-10-20 13:54 ` Sasha Levin
2026-10-20 14:26 ` Thorsten Leemhuis
2026-10-16 15:28 ` [PATCH v3 3/7] docs: stable-kernel-rules: drop rules the stable trees do not apply Sasha Levin
2026-10-16 15:59 ` Greg Kroah-Hartman
2026-10-16 16:01 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin
2026-10-17 16:44 ` SJ Park
2026-10-16 15:28 ` [PATCH v3 4/7] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-16 16:04 ` Bradley Morgan
2026-10-16 15:28 ` [PATCH v3 5/7] agents: add a skill to determine stable tags Sasha Levin
2026-10-16 16:04 ` Bradley Morgan
2026-10-16 15:28 ` [PATCH v3 6/7] agents: add a skill to find other instances of a fixed bug Sasha Levin
2026-10-16 16:05 ` Bradley Morgan
2026-10-16 18:00 ` Julia Lawall
2026-10-16 18:09 ` Sasha Levin
2026-10-16 18:17 ` Julia Lawall
2026-10-16 18:32 ` Sasha Levin
2026-10-16 15:28 ` [PATCH v3 7/7] agents: add a skill to write commit messages Sasha Levin
2026-10-16 16:05 ` Bradley Morgan
2026-10-20 13:29 ` Sasha Levin
2026-10-16 16:00 ` [PATCH v3 0/7] agents: add skills for Fixes tags, stable tags, similar bugs, and " Miguel Ojeda
2026-10-20 13:31 ` Sasha Levin [this message]
2026-10-20 16:23 ` Miguel Ojeda
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=20261020133156.3153106-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=error27@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--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=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.