* Re: [PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining
[not found] <alpine.DEB.2.21.2512072345220.49654@angie.orcam.me.uk>
@ 2026-05-06 22:30 ` Bjorn Helgaas
0 siblings, 0 replies; only message in thread
From: Bjorn Helgaas @ 2026-05-06 22:30 UTC (permalink / raw)
To: Maciej W. Rozycki, Matthew W Carlis
Cc: Bjorn Helgaas, ALOK TIWARI, ashishk, msaggi, sconnor,
Lukas Wunner, Ilpo Järvinen, Jiwei, guojinhui.liam, ahuang12,
sunjw10, linux-pci, linux-kernel
[cc->to: Matthew]
On Mon, Dec 08, 2025 at 07:24:23PM +0000, Maciej W. Rozycki wrote:
> Hi,
>
> I've figured out that backporting will be less intrusive if an update to
> use `->supported_speeds' is posted as a separate follow-up change. So it
> is now 2/3 in this series, after 1/3 comprising the original patch, only
> trivially updated. Then 3/3 moves the maximum link speed determination
> earlier on for an early exit in the PCIE_SPEED_2_5GT case; maybe unlikely,
> but essentially free now, now that we retrieve the speed anyway, and makes
> code a little simpler yet.
>
> Please let me know if you'd prefer me to fold 2/3 into 1/3 after all.
>
> Previous iterations:
>
> - v1 at: <https://lore.kernel.org/r/alpine.DEB.2.21.2511290245460.36486@angie.orcam.me.uk/>.
Applied to pci/enumeration for v7.2, thanks!
Matthew, I know you saw issues with some NVMe devices [1], but I'm not
clear on whether you've tested any of those devices with this series.
If you have a chance to test the series, it would be great to know
whether it helps.
[1] https://lore.kernel.org/all/20250702052430.13716-2-mattc@purestorage.com/
^ permalink raw reply [flat|nested] only message in thread