From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Dave Jiang <dave.jiang@intel.com>, linux-pci@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>,
bhelgaas@google.com, lukas@wunner.de
Subject: Re: [PATCH] PCI/AER: Remove deprecated documentation for pcie_enable_pcie_error_reporting()
Date: Tue, 14 Feb 2023 09:37:34 -0800 [thread overview]
Message-ID: <9d131247-8196-7979-d267-51325dff9281@linux.intel.com> (raw)
In-Reply-To: <167639333373.777843.2141436875951823865.stgit@djiang5-mobl3.local>
On 2/14/23 8:48 AM, Dave Jiang wrote:
> With commit [1] upstream that enables AER reporting by default for all PCIe
> devices, the documentation for pcie_enable_pcie_error_reporting() is no
/s/pcie_enable_pcie_error_reporting/pci_enable_pcie_error_reporting
> longer necessary. Remove references to the helper function.
Before removing the documentation, are the references removed from the
code? I think Bjorn only cleaned up the net drivers.
>
> [1]: commit f26e58bf6f54 ("PCI/AER: Enable error reporting when AER is native")
>
> Suggested-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/PCI/pcieaer-howto.rst | 18 ------------------
> 1 file changed, 18 deletions(-)
>
> diff --git a/Documentation/PCI/pcieaer-howto.rst b/Documentation/PCI/pcieaer-howto.rst
> index 0b36b9ebfa4b..a82802795a06 100644
> --- a/Documentation/PCI/pcieaer-howto.rst
> +++ b/Documentation/PCI/pcieaer-howto.rst
> @@ -135,15 +135,6 @@ hierarchy and links. These errors do not include any device specific
> errors because device specific errors will still get sent directly to
> the device driver.
>
> -Configure the AER capability structure
> ---------------------------------------
> -
> -AER aware drivers of PCI Express component need change the device
> -control registers to enable AER. They also could change AER registers,
> -including mask and severity registers. Helper function
> -pci_enable_pcie_error_reporting could be used to enable AER. See
> -section 3.3.
> -
> Provide callbacks
> -----------------
>
> @@ -214,15 +205,6 @@ to mmio_enabled.
>
> helper functions
> ----------------
> -::
> -
> - int pci_enable_pcie_error_reporting(struct pci_dev *dev);
> -
> -pci_enable_pcie_error_reporting enables the device to send error
> -messages to root port when an error is detected. Note that devices
> -don't enable the error reporting by default, so device drivers need
> -call this function to enable it.
> -
> ::
>
> int pci_disable_pcie_error_reporting(struct pci_dev *dev);
>
>
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2023-02-14 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:48 [PATCH] PCI/AER: Remove deprecated documentation for pcie_enable_pcie_error_reporting() Dave Jiang
2023-02-14 17:28 ` Bjorn Helgaas
2023-02-14 17:37 ` Dave Jiang
2023-02-15 14:02 ` Stefan Roese
2023-02-14 19:16 ` Sathyanarayanan Kuppuswamy
2023-02-14 17:37 ` Sathyanarayanan Kuppuswamy [this message]
2023-02-14 17:42 ` Dave Jiang
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=9d131247-8196-7979-d267-51325dff9281@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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