From: "tip-bot for travis@sgi.com" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, travis@sgi.com, linux-kernel@vger.kernel.org,
russ.anderson@hpe.com, tglx@linutronix.de, hpa@zytor.com,
mike.travis@hpe.com
Subject: [tip:x86/platform] x86/platform/UV/NMI: Fix uneccessary kABI breakage
Date: Thu, 16 Feb 2017 03:19:27 -0800 [thread overview]
Message-ID: <tip-d48085f0716f195ee7432de2dd110e2093c40fd5@git.kernel.org> (raw)
In-Reply-To: <20170215001129.068078379@asylum.americas.sgi.com>
Commit-ID: d48085f0716f195ee7432de2dd110e2093c40fd5
Gitweb: http://git.kernel.org/tip/d48085f0716f195ee7432de2dd110e2093c40fd5
Author: travis@sgi.com <travis@sgi.com>
AuthorDate: Tue, 14 Feb 2017 18:11:29 -0600
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 16 Feb 2017 12:16:52 +0100
x86/platform/UV/NMI: Fix uneccessary kABI breakage
The addition of support for UV Hubless systems unneccessarily broke
the kABI for a symbol that is not used by external kernel modules.
Remove the symbol from the EXPORT list.
Signed-off-by: Mike Travis <mike.travis@hpe.com>
Reviewed-by: Russ Anderson <russ.anderson@hpe.com>
Link: http://lkml.kernel.org/r/20170215001129.068078379@asylum.americas.sgi.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/platform/uv/uv_nmi.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/platform/uv/uv_nmi.c b/arch/x86/platform/uv/uv_nmi.c
index 0ecd7bf..9743d0c 100644
--- a/arch/x86/platform/uv/uv_nmi.c
+++ b/arch/x86/platform/uv/uv_nmi.c
@@ -65,7 +65,6 @@
static struct uv_hub_nmi_s **uv_hub_nmi_list;
DEFINE_PER_CPU(struct uv_cpu_nmi_s, uv_cpu_nmi);
-EXPORT_PER_CPU_SYMBOL_GPL(uv_cpu_nmi);
/* UV hubless values */
#define NMI_CONTROL_PORT 0x70
parent reply other threads:[~2017-02-16 11:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170215001129.068078379@asylum.americas.sgi.com>]
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-d48085f0716f195ee7432de2dd110e2093c40fd5@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@kernel.org \
--cc=russ.anderson@hpe.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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
all inboxes | Powered by JetHome®