From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
bcm-kernel-feedback-list@broadcom.com,
jonathan.derrick@linux.dev, kw@linux.com,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-renesas-soc@vger.kernel.org,
lpieralisi@kernel.org, marek.vasut+renesas@gmail.com,
minghuan.Lian@nxp.com, mingkai.hu@nxp.com,
m.karthikeyan@mobiveil.co.in, nirmal.patel@linux.intel.com,
rjui@broadcom.com, robh@kernel.org, roy.zang@nxp.com,
sbranden@broadcom.com, yoshihiro.shimoda.uh@renesas.com,
Zhiqiang.Hou@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] PCI: PCI_HEADER_TYPE bugfix & cleanups
Date: Tue, 3 Oct 2023 11:58:08 -0500 [thread overview]
Message-ID: <20231003165808.GA677787@bhelgaas> (raw)
In-Reply-To: <20231003125300.5541-1-ilpo.jarvinen@linux.intel.com>
On Tue, Oct 03, 2023 at 03:52:57PM +0300, Ilpo Järvinen wrote:
> One bugfix and cleanups for PCI_HEADER_TYPE_* literals.
>
> This series only covers what's within drivers/pci/. I'd have patches
> for other subsystems too but I decided to wait with them until
> PCI_HEADER_TYPE_MFD is in Linus' tree (to keep the series receipient
> count reasonable, the rest can IMO go through the subsystem specific
> trees once the define is there).
>
> Ilpo Järvinen (3):
> PCI: vmd: Correct PCI Header Type Register's MFD bit check
> PCI: Add PCI_HEADER_TYPE_MFD pci_regs.h
> PCI: Use PCI_HEADER_TYPE_* instead of literals
>
> drivers/pci/controller/dwc/pci-layerscape.c | 2 +-
> .../controller/mobiveil/pcie-mobiveil-host.c | 2 +-
> drivers/pci/controller/pcie-iproc.c | 2 +-
> drivers/pci/controller/pcie-rcar-ep.c | 2 +-
> drivers/pci/controller/pcie-rcar-host.c | 2 +-
> drivers/pci/controller/vmd.c | 5 ++---
> drivers/pci/hotplug/cpqphp_ctrl.c | 6 ++---
> drivers/pci/hotplug/cpqphp_pci.c | 22 +++++++++----------
> drivers/pci/hotplug/ibmphp.h | 5 +++--
> drivers/pci/hotplug/ibmphp_pci.c | 2 +-
> drivers/pci/pci.c | 2 +-
> drivers/pci/quirks.c | 6 ++---
> include/uapi/linux/pci_regs.h | 1 +
> 13 files changed, 30 insertions(+), 29 deletions(-)
Applied to pci/enumeration for v6.7, thanks!
prev parent reply other threads:[~2023-10-03 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 12:52 [PATCH 0/3] PCI: PCI_HEADER_TYPE bugfix & cleanups Ilpo Järvinen
2023-10-03 12:52 ` [PATCH 1/3] PCI: vmd: Correct PCI Header Type Register's MFD bit check Ilpo Järvinen
2023-10-03 12:52 ` [PATCH 2/3] PCI: Add PCI_HEADER_TYPE_MFD pci_regs.h Ilpo Järvinen
2023-10-03 12:53 ` [PATCH 3/3] PCI: Use PCI_HEADER_TYPE_* instead of literals Ilpo Järvinen
2023-10-03 13:07 ` Wolfram Sang
2023-10-03 16:58 ` 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=20231003165808.GA677787@bhelgaas \
--to=helgaas@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jonathan.derrick@linux.dev \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lpieralisi@kernel.org \
--cc=m.karthikeyan@mobiveil.co.in \
--cc=marek.vasut+renesas@gmail.com \
--cc=minghuan.Lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=nirmal.patel@linux.intel.com \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=roy.zang@nxp.com \
--cc=sbranden@broadcom.com \
--cc=yoshihiro.shimoda.uh@renesas.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).