From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linuxppc-dev@lists.ozlabs.org,
Oliver O'Halloran <oohall@gmail.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [PATCH 0/2] PCI/AER: Remove/unexport error reporting enable/disable
Date: Thu, 13 Jul 2023 11:18:22 -0500 [thread overview]
Message-ID: <20230713161822.GA320898@bhelgaas> (raw)
In-Reply-To: <20230710232136.233034-1-helgaas@kernel.org>
On Mon, Jul 10, 2023 at 06:21:34PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> pci_disable_pcie_error_reporting() is unused; remove it.
> pci_enable_pcie_error_reporting() is used only inside aer.c; make it
> static.
>
> Bjorn Helgaas (2):
> PCI/AER: Drop unused pci_disable_pcie_error_reporting()
> PCI/AER: Unexport pci_enable_pcie_error_reporting()
>
> drivers/pci/pcie/aer.c | 15 +--------------
> include/linux/aer.h | 11 -----------
> 2 files changed, 1 insertion(+), 25 deletions(-)
Applied to pci/aer for v6.6, thanks Christoph and Sathy!
prev parent reply other threads:[~2023-07-13 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 23:21 [PATCH 0/2] PCI/AER: Remove/unexport error reporting enable/disable Bjorn Helgaas
2023-07-10 23:21 ` [PATCH 1/2] PCI/AER: Drop unused pci_disable_pcie_error_reporting() Bjorn Helgaas
2023-07-11 5:11 ` Christoph Hellwig
2023-07-10 23:21 ` [PATCH 2/2] PCI/AER: Unexport pci_enable_pcie_error_reporting() Bjorn Helgaas
2023-07-11 5:11 ` Christoph Hellwig
2023-07-11 1:18 ` [PATCH 0/2] PCI/AER: Remove/unexport error reporting enable/disable Sathyanarayanan Kuppuswamy
2023-07-13 16:18 ` Bjorn Helgaas [this message]
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=20230713161822.GA320898@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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