From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>
Cc: linux-pci@vger.kernel.org,
"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Cyril Brulebois" <kibi@debian.org>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v3 0/2] PCI: brcmstb: Add panic/die handler to driver
Date: Tue, 28 Oct 2025 13:07:08 -0500 [thread overview]
Message-ID: <20251028180708.GA1523449@bhelgaas> (raw)
In-Reply-To: <176094292821.11548.4875305934446802597.b4-ty@kernel.org>
[+cc Ilpo]
On Mon, Oct 20, 2025 at 12:18:48PM +0530, Manivannan Sadhasivam wrote:
> On Fri, 03 Oct 2025 15:56:05 -0400, Jim Quinlan wrote:
> > v3 Changes:
> > -- Commit "Add a way to indicate if PCIe bridge is active"
> > o Implement Bjorn's V1 suggestion properly (Bjorn, Mani)
> > o Remove unrelated change in commit (Mani)
> > o Remove an "inline" directive (Mani)
> > o s/bridge_on/bridge_in_reset/ (Mani)
> > -- Commit "Add panic/die handler to driver"
> > o dev_err(...) message changed from "handling" error (Mani)
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] PCI: brcmstb: Add a way to indicate if PCIe bridge is active
> commit: 7dfe1602f6dc96f228403b930dbe0a93717bc287
> [2/2] PCI: brcmstb: Add panic/die handler to driver
> commit: 47288064f6a6ce99c3c1fd7b116011b970945273
I deferred these for now because there are some open questions that we
should resolve first:
https://lore.kernel.org/r/20251020184832.GA1144646@bhelgaas
https://lore.kernel.org/r/2b0f9620-a105-6e49-f9cb-4bac14e14ce2@linux.intel.com
next prev parent reply other threads:[~2025-10-28 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 19:56 [PATCH v3 0/2] PCI: brcmstb: Add panic/die handler to driver Jim Quinlan
2025-10-03 19:56 ` [PATCH v3 1/2] PCI: brcmstb: Add a way to indicate if PCIe bridge is active Jim Quinlan
2025-10-03 19:56 ` [PATCH v3 2/2] PCI: brcmstb: Add panic/die handler to driver Jim Quinlan
2025-10-04 5:06 ` [External] : " ALOK TIWARI
2025-10-28 20:34 ` James Quinlan
2025-10-20 18:48 ` Bjorn Helgaas
2025-10-21 11:02 ` Ilpo Järvinen
2025-10-28 22:37 ` James Quinlan
2025-10-28 21:17 ` James Quinlan
2025-10-20 6:48 ` [PATCH v3 0/2] " Manivannan Sadhasivam
2025-10-28 18:07 ` Bjorn Helgaas [this message]
2025-10-29 21:28 ` James Quinlan
2025-10-29 23:04 ` Bjorn Helgaas
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=20251028180708.GA1523449@bhelgaas \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=nsaenz@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