From: Christoph Hellwig <hch@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
David Woodhouse <dwmw@amazon.co.uk>,
Arjan van de Ven <arjan@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Andi Kleen <ak@linux.intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Jiri Kosina <jikos@kernel.org>,
Greg Kroah-Hartman <gregkh@linux-foundation.org>,
Paul Turner <pjt@google.com>
Subject: Re: x86: Meltdown/Spectre_v2 status
Date: Mon, 15 Jan 2018 06:57:36 -0800 [thread overview]
Message-ID: <20180115145736.GA3899@infradead.org> (raw)
In-Reply-To: <20180112224814.q722naei5qs76bam@treble>
On Fri, Jan 12, 2018 at 04:48:14PM -0600, Josh Poimboeuf wrote:
> Thomas, amazing job distilling some sanity out of the pandemonium.
>
> For future patch submissions, I would ask everyone to at least add
> x86@kernel.org to To: or Cc: (along with lkml). It's not only good
> etiquette to help the x86 maintainers, but it also gives those us not
> directly on Cc: a way to filter the patches into our inboxes.
It would be really good to get a real linux-x86 mailing list while
we're at it..
prev parent reply other threads:[~2018-01-15 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:44 Thomas Gleixner
2018-01-12 22:48 ` Josh Poimboeuf
2018-01-13 11:55 ` Woodhouse, David
2018-01-15 14:28 ` Josh Poimboeuf
2018-01-15 14:57 ` Christoph Hellwig [this message]
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=20180115145736.GA3899@infradead.org \
--to=hch@infradead.org \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linux-foundation.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--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 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®