From: Niklas Cassel <cassel@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
"Randolph Lin" <randolph@andestech.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Charles Mirabile" <cmirabil@redhat.com>,
tim609@andestech.com, "Damien Le Moal" <dlemoal@kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 0/3] PCI: dwc: Clean up iATU index mess
Date: Thu, 5 Feb 2026 09:04:14 +0100 [thread overview]
Message-ID: <aYRO_vQW6d_UfIZE@ryzen> (raw)
In-Reply-To: <alpine.DEB.2.21.2602041606040.12532@angie.orcam.me.uk>
On Wed, Feb 04, 2026 at 04:13:05PM +0000, Maciej W. Rozycki wrote:
> On Mon, 2 Feb 2026, Niklas Cassel wrote:
>
> > > Series looks good to me. However, I'd prefer waiting for Maciej's testing before
> > > merging.
> >
> > Maciej,
> >
> > Any chance to get a Tested-by?
> >
> > 6.19-rc8 is already out.
> >
> > Even if they are fixes, it would be nice if it they could make it for 7.0.
>
> Hectic time here. I've verified it now using the system I've originally
> encountered the regression with. No significant change in the kernel log
> compared to the previous fix by Krishna, except for different IRQ numbers
> assigned to devices (but that I reckon could be something else present in
> the pci tree that isn't there in Linus's master), and the system seems to
> boot correctly, so I do hope all is in order.
Thank you for testing!
Considering that it is fixes, I suggest that we queue it up for 6.20 / 7.0,
even though it will not have time to be in linux-next for a week.
(The requirement to spend time in linux-next is for new stuff, not for fixes.)
Kind regards,
Niklas
next prev parent reply other threads:[~2026-02-05 8:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 15:10 [PATCH v5 0/3] PCI: dwc: Clean up iATU index mess Niklas Cassel
2026-01-27 15:10 ` [PATCH v5 1/3] PCI: dwc: Fix msg_atu_index assignment Niklas Cassel
2026-01-28 6:07 ` Hans Zhang
2026-01-28 6:36 ` Damien Le Moal
2026-02-04 16:04 ` Maciej W. Rozycki
2026-01-27 15:10 ` [PATCH v5 2/3] PCI: dwc: Clean up iATU index usage in dw_pcie_iatu_setup() Niklas Cassel
2026-01-27 18:14 ` Frank Li
2026-01-28 6:10 ` Hans Zhang
2026-01-28 6:37 ` Damien Le Moal
2026-02-04 16:05 ` Maciej W. Rozycki
2026-01-27 15:10 ` [PATCH v5 3/3] PCI: dwc: Fix missing iATU setup when ECAM is enabled Niklas Cassel
2026-01-27 18:16 ` Frank Li
2026-01-28 6:11 ` Hans Zhang
2026-01-28 6:40 ` Damien Le Moal
2026-02-04 16:05 ` Maciej W. Rozycki
2026-01-28 8:02 ` [PATCH v5 0/3] PCI: dwc: Clean up iATU index mess Manivannan Sadhasivam
2026-02-02 12:47 ` Niklas Cassel
2026-02-04 16:13 ` Maciej W. Rozycki
2026-02-05 8:04 ` Niklas Cassel [this message]
2026-02-05 12:56 ` Manivannan Sadhasivam
2026-02-05 13:23 ` Niklas Cassel
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=aYRO_vQW6d_UfIZE@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=cmirabil@redhat.com \
--cc=dlemoal@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=macro@orcam.me.uk \
--cc=mani@kernel.org \
--cc=randolph@andestech.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tim609@andestech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.