From: Jakub Kicinski <kuba@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [ANNOUNCE] AUTOSEL: Modern AI-powered Linux Kernel Stable Backport Classifier
Date: Wed, 7 May 2025 08:54:21 -0700 [thread overview]
Message-ID: <20250507085421.7fefd093@kernel.org> (raw)
In-Reply-To: <aBt3D3z0Ayn6R_YO@lappy>
On Wed, 7 May 2025 11:06:55 -0400 Sasha Levin wrote:
> On Tue, May 06, 2025 at 07:21:59AM -0700, Jakub Kicinski wrote:
> >On Mon, 5 May 2025 14:11:20 -0400 Sasha Levin wrote:
> >> - Detailed explanations of backporting decisions
> >
> >Are those available publicly or just to the person running the tool?
> >I was scratching my hard quite a bit on the latest batch.
>
> Yup, it presents it to the person running the tool. In theory you can
> always go back and re-run whatever commit you'd like with the same query
> and get a very similar explanation, so I didn't consider storing the
> results.
Injecting the explanation under the --- separator in the AUTOSEL email
would be ideal, but not sure how hard that is to arrange.
> >> - Extensive test coverage and validation
> >
> >Would be great to hear more. My very subjective feeling is that
> >the last batch of AUTOSEL is much worse than the previous.
> >Easily 50% of false positives.
>
> "last batch" as in the big one I've sent out on Monday, or the small one
> I sent on Tuesday?
The big one on Monday.
next prev parent reply other threads:[~2025-05-07 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 18:11 Sasha Levin
2025-05-06 14:21 ` Jakub Kicinski
2025-05-07 15:06 ` Sasha Levin
2025-05-07 15:54 ` Jakub Kicinski [this message]
2025-05-27 14:47 ` 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=20250507085421.7fefd093@kernel.org \
--to=kuba@kernel.org \
--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