ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Mark Brown <broonie@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jiri Kosina <jkosina@suse.com>,
	ksummit@lists.linux.dev, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [MAINTAINERS SUMMIT] The amount of -stable emails
Date: Wed, 6 Aug 2025 17:35:42 -0400	[thread overview]
Message-ID: <aJPKrlaz9jYeRo43@lappy> (raw)
In-Reply-To: <20250806145743.GB778805@mit.edu>

On Wed, Aug 06, 2025 at 10:57:43AM -0400, Theodore Ts'o wrote:
>On Wed, Aug 06, 2025 at 01:24:47PM +0100, Mark Brown wrote:
>> On Wed, Aug 06, 2025 at 08:20:02AM -0400, Sasha Levin wrote:
>> > On Wed, Aug 06, 2025 at 11:42:03AM +0100, Mark Brown wrote:
>>
>> > > TBH I think a summary would help there - currently you're looking at six
>> > > threads for all the different stables and have to check every patch in
>> > > each, if we were instead getting a summary that says that patch A has
>> > > been backported to stables X-Y then it'd highlight more clearly if
>> > > something wasn't pulled far enough back.
>>
>> > Something along the lines of
>> > https://lore.kernel.org/all/20250805130945.471732-1-sashal@kernel.org/ ?
>>
>> Yes.  Possibly also putting the range in the body in case people find
>> that more visible when reading the thread?
>
>This is a bit of a tangent, but something that I think would be
>*really* cool is if there was a web dashboard which displayed commits
>that were either (a) tagged with a Fixes: or cc: stable, (b)
>explicitly requested by a maintainer / developer, (c) backported
>because it was a dependency needed for (a) or (b), and showed links to
>commits to the LTS links where it was a backported, and optionally a
>link to the "couldn't backport automatically" e-mail if it couldn't be
>backported.  It would also be useful if dashboard reported whether
>there was a CVE associated with the commit.
>
>The dashboard should be searchable by subsystem, and/or by date or
>kernel version range.  And it would be nice if maintainers could
>subscribe to periodic update e-mails on a per-subsystem basis.
>
>If we think this would be useful, perhaps we could try to see if we
>could get LF funding/support to create such a developer tool?

I had a similar idea about two months ago, and came up with
https://sashalevin.github.io/ . This is very much work in progress and I
wouldn't rely on the data currently in the dashboard.

Due to travel in the last couple of weeks progress was blocked, but I'm
hoping to have this in a good state for LPC to showcase it and get some
feedback in person. I wrote down your ideas around subsystem filtering,
CVE integration, and date filtering. Thanks! :)

This is one of the things AI has enabled me to do. I really don't think
that we need to go to the LF to get funding for this, at least not for
the 90% of the benefit that the dashboard will provide.

Sasha Levin, web developer, at your service :)

-- 
Thanks,
Sasha

  reply	other threads:[~2025-08-06 21:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 15:38 Jiri Kosina
2025-08-05 16:08 ` Mark Brown
2025-08-05 16:28   ` Steven Rostedt
2025-08-05 16:41     ` Mark Brown
2025-08-06  8:04       ` Geert Uytterhoeven
2025-08-06 10:42         ` Mark Brown
2025-08-06 12:20           ` Sasha Levin
2025-08-06 12:24             ` Mark Brown
2025-08-06 14:57               ` Theodore Ts'o
2025-08-06 21:35                 ` Sasha Levin [this message]
2025-08-05 17:14     ` Sasha Levin
2025-08-05 17:59       ` Konstantin Ryabitsev
2025-08-05 21:04         ` Sasha Levin
2025-08-05 17:40     ` Chuck Wolber
2025-08-05 16:49 ` James Bottomley
2025-08-05 17:26   ` Sasha Levin
2025-08-05 17:33     ` James Bottomley
2025-08-05 18:01       ` Sasha Levin
2025-08-06  8:04       ` Greg KH
2025-08-05 17:34   ` Greg KH
2025-08-05 21:39     ` Jiri Kosina
2025-08-05 22:34       ` Martin K. Petersen
2025-08-06  5:44         ` Tomasz Figa
2025-08-06  6:27       ` Takashi Iwai
2025-08-06  7:00         ` Jiri Kosina
2025-08-06  7:08           ` Takashi Iwai
2025-08-12 17:19         ` Steven Rostedt

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=aJPKrlaz9jYeRo43@lappy \
    --to=sashal@kernel.org \
    --cc=broonie@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.com \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=tytso@mit.edu \
    /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