From: Santosh Sivaraj <santosh@fossix.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Reza Arbab <arbab@linux.ibm.com>,
Balbir Singh <bsingharora@gmail.com>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
christophe leroy <christophe.leroy@c-s.fr>
Subject: [PATCH v8 2/7] powerpc/mce: Make machine_check_ue_event() static
Date: Wed, 7 Aug 2019 20:26:55 +0530 [thread overview]
Message-ID: <20190807145700.25599-3-santosh@fossix.org> (raw)
In-Reply-To: <20190807145700.25599-1-santosh@fossix.org>
From: Reza Arbab <arbab@linux.ibm.com>
The function doesn't get used outside this file, so make it static.
Signed-off-by: Reza Arbab <arbab@linux.ibm.com>
Signed-off-by: Santosh Sivaraj <santosh@fossix.org>
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
---
arch/powerpc/kernel/mce.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/kernel/mce.c b/arch/powerpc/kernel/mce.c
index 0ab6fa7cbbbb..8c0b471658a7 100644
--- a/arch/powerpc/kernel/mce.c
+++ b/arch/powerpc/kernel/mce.c
@@ -33,7 +33,7 @@ static DEFINE_PER_CPU(struct machine_check_event[MAX_MC_EVT],
mce_ue_event_queue);
static void machine_check_process_queued_event(struct irq_work *work);
-void machine_check_ue_event(struct machine_check_event *evt);
+static void machine_check_ue_event(struct machine_check_event *evt);
static void machine_process_ue_event(struct work_struct *work);
static struct irq_work mce_event_process_work = {
@@ -202,7 +202,7 @@ void release_mce_event(void)
/*
* Queue up the MCE event which then can be handled later.
*/
-void machine_check_ue_event(struct machine_check_event *evt)
+static void machine_check_ue_event(struct machine_check_event *evt)
{
int index;
--
2.20.1
next prev parent reply other threads:[~2019-08-07 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:56 [PATCH v8 0/7] powerpc: implement machine check safe memcpy Santosh Sivaraj
2019-08-07 14:56 ` [PATCH v8 1/7] powerpc/mce: Schedule work from irq_work Santosh Sivaraj
2019-08-09 18:55 ` Mahesh Jagannath Salgaonkar
2019-08-07 14:56 ` Santosh Sivaraj [this message]
2019-08-07 14:56 ` [PATCH v8 3/7] powerpc/mce: Fix MCE handling for huge pages Santosh Sivaraj
2019-08-09 19:06 ` Mahesh Jagannath Salgaonkar
2019-08-11 1:32 ` Santosh Sivaraj
2019-08-07 14:56 ` [PATCH v8 4/7] extable: Add function to search only kernel exception table Santosh Sivaraj
2019-08-07 14:56 ` [PATCH v8 5/7] powerpc/memcpy: Add memcpy_mcsafe for pmem Santosh Sivaraj
2019-08-07 14:56 ` [PATCH v8 6/7] powerpc/mce: Handle UE event for memcpy_mcsafe Santosh Sivaraj
2019-08-07 14:57 ` [PATCH v8 7/7] powerpc: add machine check safe copy_to_user Santosh Sivaraj
2019-08-10 9:33 ` Michael Ellerman
2019-08-11 1:35 ` Santosh Sivaraj
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=20190807145700.25599-3-santosh@fossix.org \
--to=santosh@fossix.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arbab@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).