From: Christoph Hellwig <hch@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Stefan Roese <sr@denx.de>,
Lukas Wunner <lukas@wunner.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
Stuart Hayes <stuart.w.hayes@gmail.com>,
Keith Busch <kbusch@kernel.org>,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 3/3] PCI/portdrv: Unexport pcie_port_service_register(), pcie_port_service_unregister()
Date: Thu, 20 Oct 2022 01:34:11 -0700 [thread overview]
Message-ID: <Y1EIA4kEmgywjcfq@infradead.org> (raw)
In-Reply-To: <20221019204127.44463-4-helgaas@kernel.org>
On Wed, Oct 19, 2022 at 03:41:27PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> pcie_port_service_register() and pcie_port_service_unregister() are used
> only by the pciehp, aer, dpc, and pme PCIe port service drivers, none of
> which can be modules. Unexport pcie_port_service_register() and
> pcie_port_service_unregister(). No functional change intended.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-10-20 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 20:41 [PATCH 0/3] PCI/portdrv: Squash into portdrv.c Bjorn Helgaas
2022-10-19 20:41 ` [PATCH 1/3] " Bjorn Helgaas
2022-10-20 8:33 ` Christoph Hellwig
2022-10-19 20:41 ` [PATCH 2/3] PCI/portdrv: Move private things to portdrv.c Bjorn Helgaas
2022-10-20 8:33 ` Christoph Hellwig
2022-10-19 20:41 ` [PATCH 3/3] PCI/portdrv: Unexport pcie_port_service_register(), pcie_port_service_unregister() Bjorn Helgaas
2022-10-20 8:34 ` Christoph Hellwig [this message]
2022-10-19 20:44 ` [PATCH 0/3] PCI/portdrv: Squash into portdrv.c Keith Busch
2022-10-24 20:15 ` Bjorn Helgaas
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=Y1EIA4kEmgywjcfq@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sr@denx.de \
--cc=stuart.w.hayes@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