From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
kvm@vger.kernel.org
Subject: [PATCH v4 1/5] powerpc/eeh: Export eeh_iommu_group_to_pe()
Date: Thu, 7 Aug 2014 12:47:16 +1000 [thread overview]
Message-ID: <1407379640-13065-2-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
In-Reply-To: <1407379640-13065-1-git-send-email-gwshan@linux.vnet.ibm.com>
The function is used by VFIO driver, which might be built as a
dynamic module. So it should be exported.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
---
arch/powerpc/kernel/eeh.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/kernel/eeh.c b/arch/powerpc/kernel/eeh.c
index 6043879..59a64f8 100644
--- a/arch/powerpc/kernel/eeh.c
+++ b/arch/powerpc/kernel/eeh.c
@@ -1254,6 +1254,7 @@ struct eeh_pe *eeh_iommu_group_to_pe(struct iommu_group *group)
return edev->pe;
}
+EXPORT_SYMBOL_GPL(eeh_iommu_group_to_pe);
#endif /* CONFIG_IOMMU_API */
--
1.8.3.2
next prev parent reply other threads:[~2014-08-07 2:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 2:47 [PATCH v4 0/5] drivers/vfio: EEH Compile and compatibility Gavin Shan
2014-08-07 2:47 ` Gavin Shan [this message]
2014-08-08 3:49 ` [PATCH v4 1/5] powerpc/eeh: Export eeh_iommu_group_to_pe() Benjamin Herrenschmidt
2014-08-07 2:47 ` [PATCH v4 2/5] powerpc/eeh: Add warning message in eeh_dev_open() Gavin Shan
2014-08-08 3:50 ` Benjamin Herrenschmidt
2014-08-08 4:06 ` Alex Williamson
2014-08-07 2:47 ` [PATCH v4 3/5] drivers/vfio: Fix EEH build error Gavin Shan
2014-08-07 2:47 ` [PATCH v4 4/5] drivers/vfio: Allow EEH to be built as module Gavin Shan
2014-08-07 2:47 ` [PATCH v4 5/5] drivers/vfio: Enable VFIO if EEH is not supported Gavin Shan
2014-08-08 17:13 ` [PATCH v4 0/5] drivers/vfio: EEH Compile and compatibility Alex Williamson
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=1407379640-13065-2-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).