From: Manivannan Sadhasivam <mani@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 00/13] PCI: brcmstb: Stop using chip numbers for conditions
Date: Wed, 14 Oct 2026 22:44:32 +0530 [thread overview]
Message-ID: <as-4akoLT9L2c086@debian> (raw)
In-Reply-To: <CA+-6iNwE935j4wn4BWxs+t1qh3iRtWb0xNjZ-hRS0j-tkLx8=w@mail.gmail.com>
On Wed, Oct 14, 2026 at 10:45:32AM -0400, Jim Quinlan wrote:
> On Wed, Oct 14, 2026 at 8:05 AM Manivannan Sadhasivam <mani@kernel.org> wrote:
> >
> >
> > On Fri, 11 Sep 2026 19:35:25 -0400, Jim Quinlan wrote:
> > > PCI: brcmstb: Stop using chip numbers for conditions
> > >
> > > Much of the brcmstb PCIe driver code does (essentially) this:
> > >
> > > if (pcie->chip == 0x1234 || pcie->chip == 0x5678) {
> > > /* ... */
> > > }
> > >
> > > [...]
> >
> > Applied, thanks!
>
> Hi Manivannan,
>
> I apologize for not submitting a V2 promptly -- I thought that only
> Sashiko was waiting for me :-).
> I have a V2 series, where 10 V1 commits are unchanged, 3 are modified,
> and 5 are new.
> Shall I submit the changed/new commits in a new series since you have
> applied V1?
>
Yeah, please do!
- Mani
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2026-10-14 17:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 23:35 [PATCH 00/13] PCI: brcmstb: Stop using chip numbers for conditions Jim Quinlan
2026-09-11 23:35 ` [PATCH 01/13] PCI: brcmstb: Remove redundant const specifier for struct fields Jim Quinlan
2026-09-16 23:59 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 02/13] PCI: brcmstb: Use flags u32 instead of bools Jim Quinlan
2026-09-17 0:00 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 03/13] PCI: brcmstb: Add Broadcom quirks macro Jim Quinlan
2026-09-17 0:00 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 04/13] PCI: brcmstb: Declare and assign quirk OB_WIN_32BIT_ADDR Jim Quinlan
2026-09-17 0:01 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 05/13] PCI: brcmstb: Declare and assign quirk OB_WIN_MAXSZ_128MB Jim Quinlan
2026-09-17 0:01 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 06/13] PCI: brcmstb: Declare and assign flag IS_BMIPS Jim Quinlan
2026-09-17 0:03 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 07/13] PCI: brcmstb: Declare and assign quirk 32BIT_PCI_OPS Jim Quinlan
2026-09-17 16:06 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 08/13] PCI: brcmstb: Declare and assign quirk NO_RGR1_TIMER Jim Quinlan
2026-09-17 17:01 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 09/13] PCI: brcmstb: Declare and assign quirk EARLY_PERST_ASSERT Jim Quinlan
2026-09-17 17:01 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 10/13] PCI: brcmstb: Declare and assign quirk PERST_PCIE_REV_CUTOFF Jim Quinlan
2026-09-17 17:02 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 11/13] PCI: brcmstb: Put max_burst_size setting in cfg_data Jim Quinlan
2026-09-17 17:05 ` Florian Fainelli
2026-09-17 18:07 ` Jim Quinlan
2026-09-11 23:35 ` [PATCH 12/13] PCI: brcmstb: Use order-0 indexing for inbound BAR window array Jim Quinlan
2026-09-17 17:08 ` Florian Fainelli
2026-09-11 23:35 ` [PATCH 13/13] PCI: brcmstb: Split up complicated function into two variants Jim Quinlan
2026-09-17 17:09 ` Florian Fainelli
2026-10-14 7:40 ` [PATCH 00/13] PCI: brcmstb: Stop using chip numbers for conditions Manivannan Sadhasivam
2026-10-14 12:05 ` Manivannan Sadhasivam
2026-10-14 14:45 ` Jim Quinlan
2026-10-14 17:14 ` Manivannan Sadhasivam [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=as-4akoLT9L2c086@debian \
--to=mani@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=nsaenz@kernel.org \
--cc=robh@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