From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Steven Rostedt <rostedt@goodmis.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit?
Date: Mon, 10 Aug 2026 09:32:24 -0400 [thread overview]
Message-ID: <cc6505e586325cd59ba036cef5429039c9c71ba8.camel@HansenPartnership.com> (raw)
In-Reply-To: <20260810091154.2d3cd6d5@gandalf.local.home>
On Mon, 2026-08-10 at 09:11 -0400, Steven Rostedt wrote:
> On Mon, 10 Aug 2026 08:26:36 +0100
> "Lorenzo Stoakes (ARM)" <ljs@kernel.org> wrote:
>
> > > 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 ;)
>
> From my understanding of what Dave ranted about last time, MM would
> be small potatoes.
>
> I think it's because DRM has a wide arrangement of different types of
> hardware under one umbrella. It sounded to me a bit like herding
> cats.
>
> MM may be a large and critical subsystem, but most hardware acts
> pretty much the same.
Have you met some of the weird architectures with their super strange
VM extensions and the even weirder confidential computing extensions?
> Where most developers are working together on a common
> platform. Even with minor differences between architectures.
> Architecture specifics of how to create memory mappings can be mostly
> be abstracted out.
True (well mostly), but the internal complexity is concealed within an
external abstraction rather than having it spill all over the kernel
... I would hope DRM does the same.
> I don't know DRM at all, but just from listening to Dave, it sounded
> to me like everyone is doing things their own way and Dave needs to
> manage it all with a more complex process. Where networking and arm
> may be the only ones to rival the complex process of DRM.
If your assumption is correct, this is internal cat herding ... MM has
much the same problem except that it has to deal with somewhat
opinionated architecture maintainers (around 22 of them) to agree on
the internal abstractions for MM primitives. Perhaps rather than
getting into my problem is bigger than yours type arguments, we could
observe that MM might run a bit more smoothly because it gets an
additional 3 day conference (LSF/MM) plus a MC at Plumbers to sort
itself out?
Regards,
James
next prev parent reply other threads:[~2026-08-10 13:32 UTC|newest]
Thread overview: 55+ 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
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 [this message]
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 8:12 ` Dup commits in NFC trees [Was: Time to call it quits for the maintainer summit?] Matthieu Baerts
2026-08-11 3:29 ` [MAINTAINERS SUMMIT] Time to call it quits for the maintainer summit? Dave Airlie
2026-08-11 7:12 ` Geert Uytterhoeven
2026-08-11 8:16 ` Geert Uytterhoeven
2026-08-10 21:30 ` Dave Airlie
2026-08-10 21:45 ` Liam R. Howlett
2026-08-11 8:19 ` Lorenzo Stoakes (ARM)
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=cc6505e586325cd59ba036cef5429039c9c71ba8.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=ksummit@lists.linux.dev \
--cc=ljs@kernel.org \
--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.