Linux EDAC development
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Karl Mehltretter <kmehltretter@gmail.com>,
	Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
	linux-edac@vger.kernel.org, linux-doc@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] Documentation: RAS: Use the real EDAC PCI parity control names
Date: Tue, 15 Sep 2026 13:30:26 -0600	[thread overview]
Message-ID: <874ifq8g8d.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260905092441.41401-1-kmehltretter@gmail.com>

Karl Mehltretter <kmehltretter@gmail.com> writes:

> 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>
> ---
>  Documentation/admin-guide/RAS/main.rst | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2026-09-15 19:30 UTC|newest]

Thread overview: 3+ 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
2026-09-15 19:30 ` Jonathan Corbet [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=874ifq8g8d.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bp@alien8.de \
    --cc=kmehltretter@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=rdunlap@infradead.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