From: Vidya Sagar <vidyas@nvidia.com>
To: <jingoohan1@gmail.com>, <gustavo.pimentel@synopsys.com>,
<lorenzo.pieralisi@arm.com>, <bhelgaas@google.com>,
<Jisheng.Zhang@synaptics.com>, <thierry.reding@gmail.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kthota@nvidia.com>, <mmaddireddy@nvidia.com>,
<sagar.tv@gmail.com>, <vidyas@nvidia.com>
Subject: [PATCH 0/2] PCI: dwc: Export symbols to support module build
Date: Thu, 4 Apr 2019 17:50:22 +0530 [thread overview]
Message-ID: <1554380425-29215-1-git-send-email-vidyas@nvidia.com> (raw)
This patch set is based on Jisheng Zhang's <Jisheng.Zhang@synaptics.com>
patch set to support implementing .remove() hook in host controller
drivers of Designware based implementations.
Jisheng's patches: https://patchwork.kernel.org/project/linux-pci/list/?series=98559
This patch set moves config space APIs which are inlined in headers to
source files and exports them along with the other required APIs to
support building host controller drivers as modules.
Vidya Sagar (2):
PCI: dwc: Add API support to de-initialize host
PCI: dwc: Export APIs to support .remove() implementation
drivers/pci/controller/dwc/pcie-designware-host.c | 11 +++++++
drivers/pci/controller/dwc/pcie-designware.c | 38 +++++++++++++++++++++
drivers/pci/controller/dwc/pcie-designware.h | 40 +++++++----------------
3 files changed, 60 insertions(+), 29 deletions(-)
--
2.7.4
next reply other threads:[~2019-04-04 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 12:20 Vidya Sagar [this message]
2019-04-04 12:20 ` [PATCH 1/2] PCI: dwc: Add API support to de-initialize host Vidya Sagar
2019-04-16 11:21 ` vidya sagar
2019-04-16 13:39 ` Gustavo Pimentel
2019-04-04 12:20 ` [PATCH 2/2] PCI: dwc: Export APIs to support .remove() implementation Vidya Sagar
2019-04-16 13:43 ` Gustavo Pimentel
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=1554380425-29215-1-git-send-email-vidyas@nvidia.com \
--to=vidyas@nvidia.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=thierry.reding@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).