From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: cyndis@kapsi.fi, thierry.reding@gmail.com, bhelgaas@google.com,
lorenzo.pieralisi@arm.com
Cc: jonathanh@nvidia.com, robh+dt@kernel.org, frowand.list@gmail.com,
rjw@rjwysocki.net, tglx@linutronix.de, vidyas@nvidia.com,
kthota@nvidia.com, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org,
Manikanta Maddireddy <mmaddireddy@nvidia.com>
Subject: [PATCH V3 1/7] of: Export of_pci_range_to_resource()
Date: Fri, 1 Dec 2017 14:50:01 +0530 [thread overview]
Message-ID: <1512120007-28088-2-git-send-email-mmaddireddy@nvidia.com> (raw)
In-Reply-To: <1512120007-28088-1-git-send-email-mmaddireddy@nvidia.com>
Tegra PCIe host driver parses of_pci_range from device tree and converts
to resource. Export of_pci_range_to_resource() to allow Tegra PCIe host
driver to be compiled as loadable kernel module.
Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
Acked-by: Rob Herring <robh@kernel.org>
---
V2:
* commit message update
V3:
* no change in this patch
drivers/of/address.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/of/address.c b/drivers/of/address.c
index fa6cabfc3cb9..8d9b93f8701a 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -361,6 +361,7 @@ int of_pci_range_to_resource(struct of_pci_range *range,
res->end = (resource_size_t)OF_BAD_ADDR;
return err;
}
+EXPORT_SYMBOL(of_pci_range_to_resource);
#endif /* CONFIG_PCI */
/*
--
2.1.4
next prev parent reply other threads:[~2017-12-01 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 9:20 [PATCH V3 0/7] Add loadable kernel module and power management support Manikanta Maddireddy
2017-12-01 9:20 ` Manikanta Maddireddy [this message]
2017-12-01 9:20 ` [PATCH V3 3/7] PCI: tegra: Remove PCI_REASSIGN_ALL_BUS flag for Tegra PCIe Manikanta Maddireddy
[not found] ` <1512120007-28088-1-git-send-email-mmaddireddy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-12-01 9:20 ` [PATCH V3 2/7] PCI: Export pci_find_host_bridge() Manikanta Maddireddy
[not found] ` <1512120007-28088-3-git-send-email-mmaddireddy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-12-05 20:04 ` Bjorn Helgaas
[not found] ` <20171205200402.GF23510-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-12-08 8:37 ` Manikanta Maddireddy
[not found] ` <aebabb88-d894-2b1f-d3e8-63a2acad9665-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-12-08 14:38 ` Bjorn Helgaas
2017-12-01 9:20 ` [PATCH V3 4/7] PCI: tegra: Free resources on probe failure Manikanta Maddireddy
2017-12-01 9:20 ` [PATCH V3 5/7] PCI: tegra: Add loadable kernel module support Manikanta Maddireddy
2017-12-01 9:20 ` [PATCH V3 7/7] PCI: tegra: Add power management support Manikanta Maddireddy
2018-01-12 18:10 ` [PATCH V3 0/7] Add loadable kernel module and " Lorenzo Pieralisi
2017-12-01 9:20 ` [PATCH V3 6/7] PCI: tegra: Broadcast PME_Turn_Off message before link goes to L2 Manikanta Maddireddy
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=1512120007-28088-2-git-send-email-mmaddireddy@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=cyndis@kapsi.fi \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kthota@nvidia.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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).