From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, luto@kernel.org
Subject: Re: [PATCH 0/3] [RFC] x86: start the MPX removal process
Date: Wed, 22 Jan 2020 14:09:13 +0100 [thread overview]
Message-ID: <20200122130913.GA20584@zn.tnic> (raw)
In-Reply-To: <20190705175317.1B3C9C52@viggo.jf.intel.com>
On Fri, Jul 05, 2019 at 10:53:17AM -0700, Dave Hansen wrote:
> This series is also available here, and will get some additional 0day
> testing to ensure no funkiness:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-mpx.git mpx-remove-201907
>
> While there's no rocket science in here, this is probably not ready
> to be pulled until 0day has the weekend to churn on it.
And whoops, half a year passed. :-)
Should we try removing it again? This time I won't stop until it's gone.
:-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-01-22 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 17:53 [PATCH 0/3] [RFC] x86: start the MPX removal process Dave Hansen
2019-07-05 17:53 ` [PATCH 1/3] x86/mpx: remove selftests Makefile entry Dave Hansen
2019-07-22 9:58 ` [tip:x86/cleanups] x86/mpx: Remove " tip-bot for Dave Hansen
2019-07-05 17:53 ` [PATCH 2/3] x86/mpx: remove selftests themselves Dave Hansen
2019-07-22 9:58 ` [tip:x86/cleanups] x86/mpx: Remove " tip-bot for Dave Hansen
2019-07-05 17:53 ` [PATCH 3/3] x86/mpx: remove MPX APIs Dave Hansen
2019-07-22 9:59 ` [tip:x86/cleanups] x86/mpx: Remove " tip-bot for Dave Hansen
2020-01-22 13:09 ` Borislav Petkov [this message]
2020-01-22 18:14 ` [PATCH 0/3] [RFC] x86: start the MPX removal process Dave Hansen
2020-01-23 11:23 ` 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=20200122130913.GA20584@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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