public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] PCI: cpqphp: Fix and cleanups
Date: Tue, 22 Oct 2024 10:08:52 -0500	[thread overview]
Message-ID: <20241022150852.GA878966@bhelgaas> (raw)
In-Reply-To: <20241022091140.3504-1-ilpo.jarvinen@linux.intel.com>

On Tue, Oct 22, 2024 at 12:11:36PM +0300, Ilpo Järvinen wrote:
> Fix one PCIBIOS_* return value confusion in cpqphp and cleanup a few
> other things.
> 
> v2:
> - Add a warning print if the path missing recursion is executed.
> 
> Ilpo Järvinen (4):
>   PCI: cpqphp: Fix PCIBIOS_* return value confusions
>   PCI: cpqphp: Use pci_bus_read_dev_vendor_id() to detect presence
>   PCI: cpqphp: Use define to read class/revision dword
>   PCI: cpqphp: Simplify PCI_ScanBusForNonBridge()
> 
>  drivers/pci/hotplug/cpqphp_pci.c | 47 +++++++++++++-------------------
>  1 file changed, 19 insertions(+), 28 deletions(-)

Applied to pci/hotplug for v6.13, thanks!

      parent reply	other threads:[~2024-10-22 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22  9:11 [PATCH v2 0/4] PCI: cpqphp: Fix and cleanups Ilpo Järvinen
2024-10-22  9:11 ` [PATCH v2 1/4] PCI: cpqphp: Fix PCIBIOS_* return value confusions Ilpo Järvinen
2024-10-22  9:11 ` [PATCH v2 2/4] PCI: cpqphp: Use pci_bus_read_dev_vendor_id() to detect presence Ilpo Järvinen
2024-10-22  9:11 ` [PATCH v2 3/4] PCI: cpqphp: Use define to read class/revision dword Ilpo Järvinen
2024-10-22  9:11 ` [PATCH v2 4/4] PCI: cpqphp: Simplify PCI_ScanBusForNonBridge() Ilpo Järvinen
2024-10-22 15:08 ` 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=20241022150852.GA878966@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --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