From: Dave Hansen <dave.hansen@intel.com>
To: Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Lutomirski <luto@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Guan Xuetao <gxt@pku.edu.cn>
Subject: Re: [PATCH 0/5] x86: finish the MPX removal process
Date: Thu, 23 Jan 2020 13:23:35 -0800 [thread overview]
Message-ID: <636d5f4b-c47f-77f6-067f-a6b342db5650@intel.com> (raw)
In-Reply-To: <20200123202600.GG10328@zn.tnic>
On 1/23/20 12:26 PM, Borislav Petkov wrote:
> On Thu, Jan 23, 2020 at 11:26:38AM -0800, Linus Torvalds wrote:
>> On Thu, Jan 23, 2020 at 11:23 AM Dave Hansen
>> <dave.hansen@linux.intel.com> wrote:
>>> I'd _rather_ this go in via the x86 tree, but I'm not picky.
> Any particular reason why?
I'm confident I can send patches to the x86 maintainers and not make
them too angry. Sending pull requests to Linus, not so much. :)
I'll just plan to send it to Linus directly.
next prev parent reply other threads:[~2020-01-23 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 19:04 [PATCH 0/5] x86: finish the MPX removal process Dave Hansen
2020-01-23 19:05 ` [PATCH 4/5] mm: remove arch_bprm_mm_init() hook Dave Hansen
2020-01-23 19:26 ` [PATCH 0/5] x86: finish the MPX removal process Linus Torvalds
2020-01-23 20:26 ` Borislav Petkov
2020-01-23 20:26 ` Borislav Petkov
2020-01-23 21:23 ` Dave Hansen [this message]
2020-01-23 21:23 ` Dave Hansen
2020-01-24 0:01 ` Linus Torvalds
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=636d5f4b-c47f-77f6-067f-a6b342db5650@intel.com \
--to=dave.hansen@intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gxt@pku.edu.cn \
--cc=jdike@addtoit.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--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;
as well as URLs for NNTP newsgroup(s).