From: Dave Hansen <dave.hansen@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86: Make x86@kernel.org a list and not a maintainer
Date: Wed, 20 Aug 2025 14:44:40 -0700 [thread overview]
Message-ID: <f472c4ab-9ca2-4183-8f95-8390bc35e068@intel.com> (raw)
In-Reply-To: <20250820174103.3b3eef1e@gandalf.local.home>
On 8/20/25 14:41, Steven Rostedt wrote:
> On Wed, 20 Aug 2025 14:37:57 -0700
> Dave Hansen <dave.hansen@intel.com> wrote:
>>> The MAINTAINERS document starts with:
>>>
>>> M: *Mail* patches to: FullName <address@domain>
>>> [..]
>>> L: *Mailing list* that is relevant to this area
>> Yeah, it's not a person, but it's also not a list that folks can
>> subscribe to. So there really isn't a good fit for it. I've never heard
>> of it causing any problems, so my inclination would be to just leave it
>> as-is.
> My complaint is that it's listed as both 'L' and 'M'. It should at least be
> consistent.
Ahh, gotcha. I didn't realize how many entries we had pointing to it!
The main one is:
X86 ARCHITECTURE (32-BIT AND 64-BIT)
...
M: x86@kernel.org
so if we're going to be making it consistent, I'd move them all over to
M:, not L:.
But I'm still not seeing much of a problem here. :)
next prev parent reply other threads:[~2025-08-20 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 19:20 Steven Rostedt
2025-08-20 21:37 ` Dave Hansen
2025-08-20 21:41 ` Steven Rostedt
2025-08-20 21:44 ` Dave Hansen [this message]
2025-08-20 21:49 ` 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=f472c4ab-9ca2-4183-8f95-8390bc35e068@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®