public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Dave Hansen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, tglx@linutronix.de,
	dave@sr71.net, mingo@kernel.org, dave.hansen@linux.intel.com
Subject: [tip:x86/mpx] fs: Do not include mpx.h in exec.c
Date: Mon, 17 Nov 2014 17:03:29 -0800	[thread overview]
Message-ID: <tip-abe1e395f6171cb2d07330c690fe0285f7f859e6@git.kernel.org> (raw)
In-Reply-To: <20141118003608.837015B3@viggo.jf.intel.com>

Commit-ID:  abe1e395f6171cb2d07330c690fe0285f7f859e6
Gitweb:     http://git.kernel.org/tip/abe1e395f6171cb2d07330c690fe0285f7f859e6
Author:     Dave Hansen <dave.hansen@linux.intel.com>
AuthorDate: Mon, 17 Nov 2014 16:36:08 -0800
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 18 Nov 2014 02:01:40 +0100

fs: Do not include mpx.h in exec.c

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.

Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Dave Hansen <dave@sr71.net>
Link: http://lkml.kernel.org/r/20141118003608.837015B3@viggo.jf.intel.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 fs/exec.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/fs/exec.c b/fs/exec.c
index 65d4f5c..01aebe3 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -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"

      reply	other threads:[~2014-11-18  1:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  0:36 [PATCH] do not include mpx.h in exec.c Dave Hansen
2014-11-18  1:03 ` tip-bot for Dave Hansen [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=tip-abe1e395f6171cb2d07330c690fe0285f7f859e6@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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