From: Bjorn Helgaas <helgaas@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: linux-pci@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Serge Semin" <Sergey.Semin@baikalelectronics.ru>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] PCI: dwc: adjust to recent removal of PCI_MSI_IRQ_DOMAIN
Date: Tue, 3 Jan 2023 14:06:01 -0600 [thread overview]
Message-ID: <20230103200601.GA1017153@bhelgaas> (raw)
In-Reply-To: <167240660288.752172.35470572785572794.b4-ty@kernel.org>
On Fri, Dec 30, 2022 at 02:23:38PM +0100, Lorenzo Pieralisi wrote:
> On Thu, 15 Dec 2022 11:34:52 +0100, Lukas Bulwahn wrote:
> > Commit a474d3fbe287 ("PCI/MSI: Get rid of PCI_MSI_IRQ_DOMAIN") removes the
> > config PCI_MSI_IRQ_DOMAIN and makes all previous references to that config
> > then refer to PCI_MSI instead.
> >
> > Commit ba6ed462dcf4 ("PCI: dwc: Add Baikal-T1 PCIe controller support")
> > adds the config PCIE_BT1, which following the previous default pattern
> > depends on the config PCI_MSI_IRQ_DOMAIN.
> >
> > [...]
>
> Applied to pci/dwc, thanks!
>
> [1/1] PCI: dwc: adjust to recent removal of PCI_MSI_IRQ_DOMAIN
> https://git.kernel.org/lpieralisi/pci/c/3c9686173220
Since both commits appeared in v6.2-rc1, I cherry-picked the fix to
for-linus so we can get it in v6.2.
Lorenzo, can you drop it from your pci/dwc branch so we don't end up
with a duplicate?
Bjorn
prev parent reply other threads:[~2023-01-03 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 10:34 [PATCH] PCI: dwc: adjust to recent removal of PCI_MSI_IRQ_DOMAIN Lukas Bulwahn
2022-12-16 15:53 ` Serge Semin
2022-12-30 13:23 ` Lorenzo Pieralisi
2023-01-03 20:06 ` 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=20230103200601.GA1017153@bhelgaas \
--to=helgaas@kernel.org \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=bhelgaas@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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