From: "tip-bot2 for kbuild test robot" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: kbuild test robot <lkp@intel.com>, Ingo Molnar <mingo@kernel.org>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: x86/mm] x86/mm/pat: Mark __cpa_flush_tlb() as static
Date: Fri, 10 Jan 2020 17:59:18 -0000 [thread overview]
Message-ID: <157867915850.30329.8747100647906961007.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20191123153023.bj6m66scjeubhbjg@4978f4969bb8>
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: da9144c5ad8943f9003ec4a6a0200637b4ba9ebd
Gitweb: https://git.kernel.org/tip/da9144c5ad8943f9003ec4a6a0200637b4ba9ebd
Author: kbuild test robot <lkp@intel.com>
AuthorDate: Sat, 23 Nov 2019 23:30:23 +08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Tue, 10 Dec 2019 10:12:55 +01:00
x86/mm/pat: Mark __cpa_flush_tlb() as static
Signed-off-by: kbuild test robot <lkp@intel.com>
Link: https://lkml.kernel.org/r/20191123153023.bj6m66scjeubhbjg@4978f4969bb8
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/mm/pat/set_memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/mm/pat/set_memory.c b/arch/x86/mm/pat/set_memory.c
index d4ab493..2082339 100644
--- a/arch/x86/mm/pat/set_memory.c
+++ b/arch/x86/mm/pat/set_memory.c
@@ -331,7 +331,7 @@ static void cpa_flush_all(unsigned long cache)
on_each_cpu(__cpa_flush_all, (void *) cache, 1);
}
-void __cpa_flush_tlb(void *data)
+static void __cpa_flush_tlb(void *data)
{
struct cpa_data *cpa = data;
unsigned int i;
prev parent reply other threads:[~2020-01-10 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 15:30 [tip:WIP.x86/mm 22/27] arch/x86/mm/pat/set_memory.c:334:6: sparse: sparse: symbol '__cpa_flush_tlb' was not declared. Should it be static? kbuild test robot
2019-11-23 15:30 ` [RFC PATCH tip] x86/mm/pat: __cpa_flush_tlb() can be static kbuild test robot
2020-01-10 17:59 ` tip-bot2 for kbuild test robot [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=157867915850.30329.8747100647906961007.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@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;
as well as URLs for NNTP newsgroup(s).