From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFD] x86: The future of MPX
Date: Wed, 2 May 2018 16:00:08 +0200 [thread overview]
Message-ID: <20180502140008.GE2851@pd.tnic> (raw)
In-Reply-To: <86ff0f5c-0215-798a-2ab8-71fe1677255c@linux.intel.com>
On Sun, Apr 29, 2018 at 09:44:00PM -0700, Dave Hansen wrote:
> The loss of the GCC support is definitely a bummer.
https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00027.html
Will go into gcc9.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-05-02 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 19:37 [RFD] x86: The future of MPX Thomas Gleixner
2018-04-28 9:18 ` Ingo Molnar
2018-04-28 16:36 ` Linus Torvalds
2018-04-28 16:44 ` Linus Torvalds
2018-04-30 4:44 ` Dave Hansen
2018-05-02 14:00 ` Borislav Petkov [this message]
2018-05-03 16:23 ` Eric W. Biederman
2018-04-28 17:50 ` Ingo Molnar
2018-04-29 4:46 ` Eric W. Biederman
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=20180502140008.GE2851@pd.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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