From: "tip-bot2 for Chen Lifu" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Chen Lifu <chenlifu@huawei.com>, Borislav Petkov <bp@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cleanups] x86/i8259: Make default_legacy_pic static
Date: Mon, 31 Oct 2022 09:29:49 -0000 [thread overview]
Message-ID: <166720858963.7716.9924110502009264129.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220823021958.3052493-1-chenlifu@huawei.com>
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: c9053e1c5a6fca221946f95d1fe6e47f69fb303a
Gitweb: https://git.kernel.org/tip/c9053e1c5a6fca221946f95d1fe6e47f69fb303a
Author: Chen Lifu <chenlifu@huawei.com>
AuthorDate: Tue, 23 Aug 2022 10:19:58 +08:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Mon, 31 Oct 2022 10:20:32 +01:00
x86/i8259: Make default_legacy_pic static
The symbol is not used outside of the file, so mark it static.
Signed-off-by: Chen Lifu <chenlifu@huawei.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/20220823021958.3052493-1-chenlifu@huawei.com
---
arch/x86/kernel/i8259.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/i8259.c b/arch/x86/kernel/i8259.c
index 15aefa3..3aa5304 100644
--- a/arch/x86/kernel/i8259.c
+++ b/arch/x86/kernel/i8259.c
@@ -407,7 +407,7 @@ struct legacy_pic null_legacy_pic = {
.make_irq = legacy_pic_uint_noop,
};
-struct legacy_pic default_legacy_pic = {
+static struct legacy_pic default_legacy_pic = {
.nr_legacy_irqs = NR_IRQS_LEGACY,
.chip = &i8259A_chip,
.mask = mask_8259A_irq,
prev parent reply other threads:[~2022-10-31 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 2:19 [PATCH -next] x86: i8259: " Chen Lifu
2022-10-31 0:48 ` chenlifu
2022-10-31 9:29 ` tip-bot2 for Chen Lifu [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=166720858963.7716.9924110502009264129.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@suse.de \
--cc=chenlifu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.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
all inboxes | Powered by JetHome®