From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: linux-edac@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Documentation: RAS: Use the real EDAC PCI parity control names
Date: Sun, 6 Sep 2026 14:28:57 -0700 [thread overview]
Message-ID: <99e7859e-5656-4bc2-b75a-5cf0ded24bf9@infradead.org> (raw)
In-Reply-To: <20260905092441.41401-1-kmehltretter@gmail.com>
On 9/5/26 2:24 AM, Karl Mehltretter wrote:
> The document names the sysfs control
> /sys/devices/system/edac/pci/check_pci_parity and the module parameter
> edac_panic_on_pci_pe. Neither exists.
>
> check_pci_parity was renamed to check_pci_errors by commit 91b99041c1d5
> ("drivers/edac: updated PCI monitoring"), after the document had been
> written.
>
> The module parameter has been edac_pci_panic_on_pe
> (drivers/edac/edac_pci_sysfs.c) since it was introduced, and the
> document described it as edac_panic_on_pci_pe from the start.
>
> Use the real names.
>
> Fixes: 91b99041c1d5 ("drivers/edac: updated PCI monitoring")
> Fixes: 327dafb1c61c ("edac: core fix redundant sysfs controls to parameters")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/admin-guide/RAS/main.rst | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/admin-guide/RAS/main.rst b/Documentation/admin-guide/RAS/main.rst
> index 5a45db32c49b..c1040e5a5b35 100644
> --- a/Documentation/admin-guide/RAS/main.rst
> +++ b/Documentation/admin-guide/RAS/main.rst
> @@ -623,7 +623,7 @@ Under ``/sys/devices/system/edac/pci`` are control and attribute files as
> follows:
>
>
> -- ``check_pci_parity`` - Enable/Disable PCI Parity checking control file
> +- ``check_pci_errors`` - Enable/Disable PCI Parity checking control file
>
> This control file enables or disables the PCI Bus Parity scanning
> operation. Writing a 1 to this file enables the scanning. Writing
> @@ -631,11 +631,11 @@ follows:
>
> Enable::
>
> - echo "1" >/sys/devices/system/edac/pci/check_pci_parity
> + echo "1" >/sys/devices/system/edac/pci/check_pci_errors
>
> Disable::
>
> - echo "0" >/sys/devices/system/edac/pci/check_pci_parity
> + echo "0" >/sys/devices/system/edac/pci/check_pci_errors
>
>
> - ``pci_parity_count`` - Parity Count
> @@ -725,15 +725,15 @@ Module parameters
>
> module/kernel parameter::
>
> - edac_panic_on_pci_pe=[0|1]
> + edac_pci_panic_on_pe=[0|1]
>
> Enable::
>
> - echo "1" > /sys/module/edac_core/parameters/edac_panic_on_pci_pe
> + echo "1" > /sys/module/edac_core/parameters/edac_pci_panic_on_pe
>
> Disable::
>
> - echo "0" > /sys/module/edac_core/parameters/edac_panic_on_pci_pe
> + echo "0" > /sys/module/edac_core/parameters/edac_pci_panic_on_pe
>
>
>
--
~Randy
prev parent reply other threads:[~2026-09-06 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:24 [PATCH] Documentation: RAS: Use the real EDAC PCI parity control names Karl Mehltretter
2026-09-06 21:28 ` Randy Dunlap [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=99e7859e-5656-4bc2-b75a-5cf0ded24bf9@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tony.luck@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