From: Dave Hansen <dave@sr71.net>
To: tglx@linutronix.de
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave@sr71.net>,
dave.hansen@linux.intel.com
Subject: [PATCH] do not include mpx.h in exec.c
Date: Mon, 17 Nov 2014 16:36:08 -0800 [thread overview]
Message-ID: <20141118003608.837015B3@viggo.jf.intel.com> (raw)
From: Dave Hansen <dave.hansen@linux.intel.com>
We no longer need mpx.h in exec.c. This will obviously also
break the build for non-x86 builds. We get the MPX includes that
we need from mmu_context.h now.
This applies on top of the MPX patches currently in the -tip
branch.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
---
b/fs/exec.c | 1 -
1 file changed, 1 deletion(-)
diff -puN fs/exec.c~no-mpx-in fs/exec.c
--- a/fs/exec.c~no-mpx-in 2014-11-17 16:22:33.935154876 -0800
+++ b/fs/exec.c 2014-11-17 16:22:39.466404410 -0800
@@ -60,7 +60,6 @@
#include <asm/uaccess.h>
#include <asm/mmu_context.h>
#include <asm/tlb.h>
-#include <asm/mpx.h>
#include <trace/events/task.h>
#include "internal.h"
_
next reply other threads:[~2014-11-18 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 0:36 Dave Hansen [this message]
2014-11-18 1:03 ` [tip:x86/mpx] fs: Do not include mpx.h in exec.c tip-bot for Dave Hansen
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=20141118003608.837015B3@viggo.jf.intel.com \
--to=dave@sr71.net \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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