From: Bjorn Helgaas <helgaas@kernel.org>
To: Emilio Perez <emiliopeju@gmail.com>
Cc: bhelgaas@google.com, corbet@lwn.net, linux-pci@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH] Documentation: pci: Use term requester ID as per standard
Date: Thu, 18 Sep 2025 17:26:47 -0500 [thread overview]
Message-ID: <20250918222647.GA1926836@bhelgaas> (raw)
In-Reply-To: <20250818023121.33427-1-emiliopeju@gmail.com>
On Mon, Aug 18, 2025 at 03:31:21AM +0100, Emilio Perez wrote:
> The PCIe standard never use the term requestor ID and therefore it might
> lead to confusion.
>
> Signed-off-by: Emilio Perez <emiliopeju@gmail.com>
Applied to pci/aer for v6.18, thanks!
I also capitalized "Requester" as a hint that this term is
specifically defined by the spec. And capitalized "PCI" in the
subject to follow historical convention for this file.
> ---
> Documentation/PCI/pcieaer-howto.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/PCI/pcieaer-howto.rst b/Documentation/PCI/pcieaer-howto.rst
> index 4b71e2f43ca7..7b30598b4fde 100644
> --- a/Documentation/PCI/pcieaer-howto.rst
> +++ b/Documentation/PCI/pcieaer-howto.rst
> @@ -138,7 +138,7 @@ error message to the Root Port above it when it captures
> an error. The Root Port, upon receiving an error reporting message,
> internally processes and logs the error message in its AER
> Capability structure. Error information being logged includes storing
> -the error reporting agent's requestor ID into the Error Source
> +the error reporting agent's requester ID into the Error Source
> Identification Registers and setting the error bits of the Root Error
> Status Register accordingly. If AER error reporting is enabled in the Root
> Error Command Register, the Root Port generates an interrupt when an
> --
> 2.50.1
>
prev parent reply other threads:[~2025-09-18 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:31 [PATCH] Documentation: pci: Use term requester ID as per standard Emilio Perez
2025-09-18 22:26 ` 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=20250918222647.GA1926836@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=emiliopeju@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/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