From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] PCI, CPER: Trivial cleanups
Date: Wed, 27 Mar 2019 08:56:06 -0500 [thread overview]
Message-ID: <20190327135606.GZ24180@google.com> (raw)
In-Reply-To: <20190325181425.247227-1-helgaas@kernel.org>
On Mon, Mar 25, 2019 at 01:14:21PM -0500, helgaas@kernel.org wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Clean up whitespace, fix some typos, add some spec references, and convert
> unnecessary __u32 usage to u32.
>
> Bjorn Helgaas (4):
> PCI: Cleanup register definition width and whitespace
> PCI: Fix comment typos
> CPER: Add UEFI spec references
> CPER: Remove unnecessary use of user-space types
These are on pci/trivial for v5.2.
> drivers/pci/controller/dwc/pci-keystone.c | 2 +-
> drivers/pci/controller/pci-host-generic.c | 2 +-
> drivers/pci/controller/pcie-iproc-msi.c | 2 +-
> drivers/pci/pci.c | 328 +++++++++++----------
> include/linux/cper.h | 336 +++++++++++-----------
> include/uapi/linux/pci_regs.h | 132 +++++----
> 6 files changed, 405 insertions(+), 397 deletions(-)
>
> --
> 2.21.0.392.gf8f6787159e-goog
>
prev parent reply other threads:[~2019-03-27 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 18:14 [PATCH 0/4] PCI, CPER: Trivial cleanups helgaas
2019-03-25 18:14 ` [PATCH 1/4] PCI: Cleanup register definition width and whitespace helgaas
2019-03-25 18:14 ` [PATCH 2/4] PCI: Fix comment typos helgaas
2019-03-30 17:56 ` Mukesh Ojha
2019-04-01 13:43 ` Bjorn Helgaas
2019-03-25 18:14 ` [PATCH 3/4] CPER: Add UEFI spec references helgaas
2019-03-25 18:14 ` [PATCH 4/4] CPER: Remove unnecessary use of user-space types helgaas
2019-03-25 18:26 ` Bjorn Helgaas
2019-03-25 19:13 ` Joe Perches
2019-03-25 19:56 ` Greg Kroah-Hartman
2019-03-30 12:52 ` Masahiro Yamada
2019-03-27 13:56 ` 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=20190327135606.GZ24180@google.com \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).