From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Mon, 10 Aug 2026 08:26:36 +0100 [thread overview]
Message-ID: <anl7CgkKb6tORavG@lucifer> (raw)
In-Reply-To: <CAPM=9tx7izyUJr_XVQju26fevzepZ-L6vs5vgH2aib9jPPjvRA@mail.gmail.com>
On Mon, Aug 10, 2026 at 08:10:21AM +1000, Dave Airlie wrote:
...
> I think people really have a misconception about what goes on at the
> maintainer summit, the best explanation I've been given was that it is
> Linus's staff meeting. The people that Linus works with closest, get
> invited to talk to Linus and help him figure out where the overall
> ship is going and where things are going wrong.
...
> Your language choice already makes it feel like you see it as some
> elite or special group. It's a bunch of technical project managers
> talking about the processes of producing the kernel. If a talk about
> the technical content of the kernel sneaks in it's very rare and also
> usually not of interest to half the room.
...
>
> > I mean I don't know, maybe it's necessary to run it as a tight ship of
> > trusted people, but I think we should at least be more clear about that.
I mean this is kinda my point.
It is being advertised as X but is actually Y. So say it's Y.
That's not what Ted's posts or the write ups or generally any comms about the MS
say it is.
The CFP-ish bit is probably pretty redundant too on this basis?
> >
> > However I wonder whether we should look at an alternative approach like
> > those with M: entries in MAINTAINERS voting on topics, or something
> > similar.
>
> Voting on what though, I'm already over the number of times
> maintainers with small potato problems think that the lives of
> maintainers with big potato problems would be much simpler if they
> just adopted their niche one-person mutt based review process.
Ah good to know core mm is small potatoes ;)
>
> Dave.
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-10 7:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 15:34 [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit? James Bottomley
2026-08-06 23:41 ` Steven Rostedt
2026-08-07 13:53 ` Rafael J. Wysocki (Intel)
2026-08-07 14:53 ` Steven Rostedt
2026-08-07 16:33 ` James Bottomley
2026-08-07 17:27 ` Linus Torvalds
2026-08-07 19:03 ` James Bottomley
2026-08-07 19:51 ` Steven Rostedt
2026-08-07 20:12 ` Shuah Khan
2026-08-09 1:51 ` Theodore Tso
2026-08-09 18:47 ` Randy Dunlap
2026-08-09 19:04 ` Jonathan Corbet
2026-08-09 21:09 ` Steven Rostedt
2026-08-10 8:14 ` Lorenzo Stoakes (ARM)
2026-08-09 21:56 ` Liam R. Howlett
2026-08-10 1:26 ` Theodore Tso
2026-08-10 2:40 ` Liam R. Howlett
2026-08-10 8:08 ` Lorenzo Stoakes (ARM)
2026-08-09 18:39 ` Lorenzo Stoakes (ARM)
2026-08-09 18:42 ` Lorenzo Stoakes (ARM)
2026-08-09 22:10 ` Dave Airlie
2026-08-10 7:26 ` Lorenzo Stoakes (ARM) [this message]
2026-08-10 7:42 ` Geert Uytterhoeven
2026-08-07 12:58 ` Laurent Pinchart
2026-08-07 13:09 ` James Bottomley
2026-08-07 13:28 ` Laurent Pinchart
2026-08-07 20:15 ` H. Peter Anvin
2026-08-07 19:15 ` Chris Mason
2026-08-07 19:53 ` Steven Rostedt
2026-08-07 23:19 ` Theodore Tso
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=anl7CgkKb6tORavG@lucifer \
--to=ljs@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=ksummit@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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.