From: Brian Norris <briannorris@chromium.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Terry Bowman <terry.bowman@amd.com>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Linas Vepstas <linasvepstas@gmail.com>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver OHalloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/4] PCI: Update error recovery documentation
Date: Thu, 11 Sep 2025 14:52:06 -0700 [thread overview]
Message-ID: <aMNEhqiJKK9NOreA@google.com> (raw)
In-Reply-To: <cover.1756451884.git.lukas@wunner.de>
On Fri, Aug 29, 2025 at 09:25:00AM +0200, Lukas Wunner wrote:
> The documentation on PCIe Advanced Error Reporting hasn't kept up with
> code changes over the years. This series seeks to remedy as many issues
> as I could find.
>
> Previous commits touching the documentation either prefixed the subject
> with "Documentation: PCI:" or (when combined with code changes) "PCI/AER:"
> or "PCI/ERR:". I chose the latter for brevity and to avoid mentioning
> "documentation" or "PCI" twice in the subject. If anyone objects or
> finds other mistakes in these patches, please let me know. Thanks!
Series looks good to my limited knowledge:
Reviewed-by: Brian Norris <briannorris@chromium.org>
prev parent reply other threads:[~2025-09-11 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 7:25 [PATCH 0/4] PCI: Update error recovery documentation Lukas Wunner
2025-08-29 7:25 ` [PATCH 1/4] PCI/AER: Sync documentation with code Lukas Wunner
2025-08-29 7:25 ` [PATCH 2/4] PCI/ERR: " Lukas Wunner
2025-08-29 7:25 ` [PATCH 3/4] PCI/ERR: Amend documentation with DPC and AER specifics Lukas Wunner
2025-08-29 8:38 ` Niklas Schnelle
2025-08-29 23:25 ` Linas Vepstas
2025-08-30 8:12 ` Lukas Wunner
2025-08-29 7:25 ` [PATCH 4/4] PCI/ERR: Tidy documentation's PCIe nomenclature Lukas Wunner
2025-09-11 21:52 ` Brian Norris [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=aMNEhqiJKK9NOreA@google.com \
--to=briannorris@chromium.org \
--cc=corbet@lwn.net \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linasvepstas@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=schnelle@linux.ibm.com \
--cc=terry.bowman@amd.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;
as well as URLs for NNTP newsgroup(s).