From: "tip-bot2 for Pavel Skripkin" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Pavel Skripkin <paskripkin@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cleanups] x86/alternatives: Make the x86nops[] symbol static
Date: Wed, 12 May 2021 11:16:06 -0000 [thread overview]
Message-ID: <162081816689.29796.6774528668273911731.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210506190726.15575-1-paskripkin@gmail.com>
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 64e1f5872a8c3d80bce4686b4ab5dbc6e6bd30c5
Gitweb: https://git.kernel.org/tip/64e1f5872a8c3d80bce4686b4ab5dbc6e6bd30c5
Author: Pavel Skripkin <paskripkin@gmail.com>
AuthorDate: Thu, 06 May 2021 22:07:26 +03:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Wed, 12 May 2021 12:22:56 +02:00
x86/alternatives: Make the x86nops[] symbol static
Sparse says:
arch/x86/kernel/alternative.c:78:21: warning: symbol 'x86nops' was not declared. Should it be static?
Since x86nops[] is not used outside this file, Sparse is right and it can be made static.
Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20210506190726.15575-1-paskripkin@gmail.com
---
arch/x86/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
index 6974b51..75c752b 100644
--- a/arch/x86/kernel/alternative.c
+++ b/arch/x86/kernel/alternative.c
@@ -75,7 +75,7 @@ do { \
} \
} while (0)
-const unsigned char x86nops[] =
+static const unsigned char x86nops[] =
{
BYTES_NOP1,
BYTES_NOP2,
prev parent reply other threads:[~2021-05-12 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 19:07 [PATCH] x86: make x86nops symbol static Pavel Skripkin
2021-05-12 11:16 ` tip-bot2 for Pavel Skripkin [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=162081816689.29796.6774528668273911731.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paskripkin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).