From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: bhelgaas@google.com, mpe@ellerman.id.au,
Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v4 3/7] powerpc/eeh: Export eeh_pe_state_mark()
Date: Thu, 29 Sep 2016 15:52:01 +1000 [thread overview]
Message-ID: <1475128325-5367-4-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
In-Reply-To: <1475128325-5367-1-git-send-email-gwshan@linux.vnet.ibm.com>
This exports eeh_pe_state_mark(). It will be used to mark the surprise
hot removed PE as isolated to avoid unexpected EEH error reporting in
surprise remove path.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
---
arch/powerpc/kernel/eeh_pe.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/kernel/eeh_pe.c b/arch/powerpc/kernel/eeh_pe.c
index f0520da..de7d091 100644
--- a/arch/powerpc/kernel/eeh_pe.c
+++ b/arch/powerpc/kernel/eeh_pe.c
@@ -581,6 +581,7 @@ void eeh_pe_state_mark(struct eeh_pe *pe, int state)
{
eeh_pe_traverse(pe, __eeh_pe_state_mark, &state);
}
+EXPORT_SYMBOL_GPL(eeh_pe_state_mark);
static void *__eeh_pe_dev_mode_mark(void *data, void *flag)
{
--
2.1.0
next prev parent reply other threads:[~2016-09-29 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 5:51 [PATCH v4 0/7] powerpc/powernv: PCI Surprise Hotplug Support Gavin Shan
2016-09-29 5:51 ` [PATCH v4 1/7] powerpc/eeh: Allow to freeze PE in eeh_pe_set_option() Gavin Shan
2016-09-29 5:52 ` [PATCH v4 2/7] powerpc/eeh: Export confirm_error_lock Gavin Shan
2016-09-29 5:52 ` Gavin Shan [this message]
2016-09-29 5:52 ` [PATCH v4 4/7] powerpc/powernv: Unfreeze PE on allocation Gavin Shan
2016-09-29 5:52 ` [PATCH v4 5/7] drivers/pci/hotplug: Remove likely() and unlikely() in powernv driver Gavin Shan
2016-09-29 5:52 ` [PATCH v4 6/7] drivers/pci/hotplug: Use of_property_read_u32() " Gavin Shan
2016-10-05 2:36 ` [v4, " Michael Ellerman
2016-09-29 5:52 ` [PATCH v4 7/7] drivers/pci/hotplug: Support surprise hotplug " Gavin Shan
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=1475128325-5367-4-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=bhelgaas@google.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).