All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Theodore Tso <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	ksummit@lists.linux.dev,
	"David Hildenbrand (Arm)" <david@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dave Airlie <airlied@gmail.com>
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Mon, 10 Aug 2026 09:20:03 -0400	[thread overview]
Message-ID: <20260810092003.5fda8e06@gandalf.local.home> (raw)
In-Reply-To: <anmHaRzbnY7rtLX8@gremlin>

On Mon, 10 Aug 2026 09:14:56 +0100
"Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:

> +cc 2*David, Liam, Andrew as referenced below
> 
> On Sun, Aug 09, 2026 at 05:09:18PM -0400, Steven Rostedt wrote:
> > This should not hinder new people from being invited. As the kernel
> > changes, new people start to have more stake in the kernel. People like
> > Miguel and I would even argue for Lorenzo ;-)  
> 
> That's very kind of you and Miguel ;)

Oops, Miguel didn't say that. I worded that wrong. Or at least I didn't add
enough commas:

  "People like Miguel, and I would even argue for, Lorenzo"

As in, People like Miguel and Lorenzo. And I would argue for you.

> 
> However I'm nowhere near the caliber of attendee the LF describes and if anybody
> from mm should attend it should be David as Liam also suggested :)
> 
> In fact as David is taking over (albeit for a transitional period) from Andrew,
> it makes sense that he be invited _this_ year in my view.

It's also about who is able to articulate issues, not just their standing in
the community. You are very vocal and able to bring up things that should
be talked about. If we have someone that is higher up the maintainer
hierarchy, but doesn't speak up, they may not be as useful.

I'm not saying that David or Liam wouldn't speak up. What I am saying is
that it's not the only criteria.

> Linus will soon be interacting with him a lot :) so he also fulfils David
> Airlie's description of the MS (which I do think is the accurate one).

It is partially Linus's "staff meeting", but to me, it's about maintainers
coming together to settle differences about what is happening within the
Linux kernel community. I view Linus as more of the "Judge" who stays
mostly quiet and just listens and then if things do not get settled between
developers, he will speak up. Similarly to what he does on the mailing list.

-- Steve

  reply	other threads:[~2026-08-10 13:20 UTC|newest]

Thread overview: 52+ 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-10 13:20             ` Steven Rostedt [this message]
2026-08-10 20:35               ` Liam R. Howlett
2026-08-10 21:05                 ` Steven Rostedt
2026-08-11  0:14                 ` Theodore Tso
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-10 14:56               ` Theodore Tso
2026-08-10 15:49                 ` 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)
2026-08-10 13:11           ` Steven Rostedt
2026-08-10 13:32             ` James Bottomley
2026-08-10 14:24               ` Steven Rostedt
2026-08-10 15:23                 ` Mark Brown
2026-08-10 15:52                   ` Randy Dunlap
2026-08-11  3:24                     ` Dave Airlie
2026-08-11  5:29                       ` Randy Dunlap
2026-08-11  6:53                         ` Geert Uytterhoeven
2026-08-10 22:47                   ` Mark Brown
2026-08-11  3:29                   ` Dave Airlie
2026-08-11  7:12                     ` Geert Uytterhoeven
2026-08-10 21:30           ` Dave Airlie
2026-08-10 21:45             ` Liam R. Howlett
2026-08-10  7:42         ` Geert Uytterhoeven
2026-08-10 15:07           ` Theodore Tso
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
2026-08-10 13:54   ` James Bottomley
2026-08-10 14:41     ` 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=20260810092003.5fda8e06@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=ksummit@lists.linux.dev \
    --cc=liam@infradead.org \
    --cc=ljs@kernel.org \
    --cc=torvalds@linux-foundation.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 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.