From: "Pali Rohár" <pali@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Tomasz Maciej Nowak <tmn505@gmail.com>,
Gregory Clement <gregory.clement@bootlin.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Xogium <contact@xogium.me>,
marek.behun@nic.cz
Subject: [PATCH v2 3/5] PCI: pci-bridge-emul: Export API functions
Date: Tue, 4 Aug 2020 13:57:45 +0200 [thread overview]
Message-ID: <20200804115747.7078-4-pali@kernel.org> (raw)
In-Reply-To: <20200804115747.7078-1-pali@kernel.org>
It allows kernel modules which are not compiled into kernel image to use
pci-bridge-emul API functions.
Signed-off-by: Pali Rohár <pali@kernel.org>
Reviewed-by: Marek Behún <marek.behun@nic.cz>
---
drivers/pci/pci-bridge-emul.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci-bridge-emul.c b/drivers/pci/pci-bridge-emul.c
index ccf26d12ec61..139869d50eb2 100644
--- a/drivers/pci/pci-bridge-emul.c
+++ b/drivers/pci/pci-bridge-emul.c
@@ -294,6 +294,7 @@ int pci_bridge_emul_init(struct pci_bridge_emul *bridge,
return 0;
}
+EXPORT_SYMBOL_GPL(pci_bridge_emul_init);
/*
* Cleanup a pci_bridge_emul structure that was previously initialized
@@ -305,6 +306,7 @@ void pci_bridge_emul_cleanup(struct pci_bridge_emul *bridge)
kfree(bridge->pcie_cap_regs_behavior);
kfree(bridge->pci_regs_behavior);
}
+EXPORT_SYMBOL_GPL(pci_bridge_emul_cleanup);
/*
* Should be called by the PCI controller driver when reading the PCI
@@ -366,6 +368,7 @@ int pci_bridge_emul_conf_read(struct pci_bridge_emul *bridge, int where,
return PCIBIOS_SUCCESSFUL;
}
+EXPORT_SYMBOL_GPL(pci_bridge_emul_conf_read);
/*
* Should be called by the PCI controller driver when writing the PCI
@@ -430,3 +433,4 @@ int pci_bridge_emul_conf_write(struct pci_bridge_emul *bridge, int where,
return PCIBIOS_SUCCESSFUL;
}
+EXPORT_SYMBOL_GPL(pci_bridge_emul_conf_write);
--
2.20.1
next prev parent reply other threads:[~2020-08-04 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 11:57 [PATCH v2 0/5] PCIe aardvark controller improvements Pali Rohár
2020-08-04 11:57 ` [PATCH v2 1/5] PCI: aardvark: Fix compilation on s390 Pali Rohár
2020-08-04 11:57 ` [PATCH v2 2/5] PCI: aardvark: Check for errors from pci_bridge_emul_init() call Pali Rohár
2020-08-04 11:57 ` Pali Rohár [this message]
2020-08-04 11:57 ` [PATCH v2 4/5] PCI: aardvark: Implement driver 'remove' function and allow to build it as module Pali Rohár
2020-08-04 11:57 ` [PATCH v2 5/5] PCI: aardvark: Move PCIe reset card code to advk_pcie_train_link() Pali Rohár
2020-08-22 9:38 ` [PATCH v2 0/5] PCIe aardvark controller improvements Pali Rohár
2020-09-07 9:40 ` Lorenzo Pieralisi
2020-09-07 11:11 ` Pali Rohár
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=20200804115747.7078-4-pali@kernel.org \
--to=pali@kernel.org \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=contact@xogium.me \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marek.behun@nic.cz \
--cc=tmn505@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).