From: Bjorn Helgaas <helgaas@kernel.org>
To: Nam Cao <namcao@linutronix.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rajesh Shah <rajesh.shah@intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] check returned value of pci_hp_add_bridge()
Date: Fri, 3 May 2024 16:29:30 -0500 [thread overview]
Message-ID: <20240503212930.GA1605242@bhelgaas> (raw)
In-Reply-To: <cover.1714762038.git.namcao@linutronix.de>
On Fri, May 03, 2024 at 09:23:18PM +0200, Nam Cao wrote:
> ...
> Nam Cao (4):
> PCI: shpchp: bail out if pci_hp_add_bridge() fails
> PCI: pciehp: bail out if pci_hp_add_bridge() fails
> PCI: hotplug: document unchecked return value of pci_hp_add_bridge()
> PCI: hotplug: remove TODO notes for sgi_hotplug
>
> drivers/pci/hotplug/TODO | 12 +++++-------
> drivers/pci/hotplug/pciehp_pci.c | 9 +++++++--
> drivers/pci/hotplug/shpchp_pci.c | 9 +++++++--
> 3 files changed, 19 insertions(+), 11 deletions(-)
I applied the last two (the TODO updates) to pci/hotplug for v6.10,
thanks!
prev parent reply other threads:[~2024-05-03 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 19:23 [PATCH 0/4] check returned value of pci_hp_add_bridge() Nam Cao
2024-05-03 19:23 ` [PATCH 1/4] PCI: shpchp: bail out if pci_hp_add_bridge() fails Nam Cao
2024-05-03 19:23 ` [PATCH 2/4] PCI: pciehp: " Nam Cao
2024-05-03 21:23 ` Bjorn Helgaas
2024-05-03 21:41 ` Nam Cao
2024-05-04 8:54 ` Lukas Wunner
2024-05-04 9:35 ` Nam Cao
2024-05-04 9:51 ` Lukas Wunner
2024-05-04 10:56 ` Nam Cao
2024-05-04 15:02 ` Lukas Wunner
2024-05-04 15:48 ` Nam Cao
2024-05-03 19:23 ` [PATCH 3/4] PCI: hotplug: document unchecked return value of pci_hp_add_bridge() Nam Cao
2024-05-03 19:23 ` [PATCH 4/4] PCI: hotplug: remove TODO notes for sgi_hotplug Nam Cao
2024-05-03 21:29 ` 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=20240503212930.GA1605242@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=rajesh.shah@intel.com \
--cc=yinghai@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