From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Borislav Petkov <bp@kernel.org>, X86 ML <x86@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/bugs: Adjust SRSO mitigation to new features
Date: Wed, 6 Nov 2024 08:27:47 -0800 [thread overview]
Message-ID: <ZyuZAzqQIXudhbxi@google.com> (raw)
In-Reply-To: <20241106162525.GHZyuYdWswAoGAUEUM@fat_crate.local>
On Wed, Nov 06, 2024, Borislav Petkov wrote:
> On Wed, Nov 06, 2024 at 08:17:38AM -0800, Sean Christopherson wrote:
> > I do subscribe to kvm@, but it's a mailing list, not at alias like x86@. AFAIK,
> > x86@ is unique in that regard. In other words, I don't see a need to document
> > the kvm@ behavior, because that's the behavior for every L: entry in MAINTAINERS
> > except the few "L: x86@kernel.org" cases.
>
> I have had maintainers in the past not like to be CCed directly as long as the
> corresponding mailing list is CCed.
LOL, doesn't that kind of defeat the purpose of MAINTAINERS?
next prev parent reply other threads:[~2024-11-06 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 10:15 [PATCH] x86/bugs: Adjust SRSO mitigation to new features Borislav Petkov
2024-11-05 0:57 ` Sean Christopherson
2024-11-05 12:34 ` Borislav Petkov
2024-11-05 18:10 ` Sean Christopherson
2024-11-05 18:56 ` Borislav Petkov
2024-11-05 19:18 ` Sean Christopherson
2024-11-05 19:24 ` Borislav Petkov
2024-11-06 15:20 ` Sean Christopherson
2024-11-06 15:29 ` Borislav Petkov
2024-11-06 15:35 ` Sean Christopherson
2024-11-06 16:13 ` Borislav Petkov
2024-11-06 16:17 ` Sean Christopherson
2024-11-06 16:25 ` Borislav Petkov
2024-11-06 16:27 ` Sean Christopherson [this message]
2024-11-06 16:39 ` Borislav Petkov
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=ZyuZAzqQIXudhbxi@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=bp@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--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 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.