mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Matthew W Carlis <mattc@purestorage.com>
Cc: ashishk@purestorage.com, msaggi@purestorage.com,
	sconnor@purestorage.com, "Lukas Wunner" <lukas@wunner.de>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	Jiwei <jiwei.sun.bj@qq.com>,
	guojinhui.liam@bytedance.com, ahuang12@lenovo.com,
	sunjw10@lenovo.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PING][PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining
Date: Thu, 19 Feb 2026 09:12:05 +0530	[thread overview]
Message-ID: <d6d04a8f-5845-4627-8cf1-a6875cb21fbb@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2602041709010.12532@angie.orcam.me.uk>



On 2/4/2026 10:42 PM, Maciej W. Rozycki wrote:
> On Mon, 8 Dec 2025, Maciej W. Rozycki wrote:
> 
>>   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.
> 
>   Ping for:
> <https://urldefense.com/v3/__https://lore.kernel.org/r/alpine.DEB.2.21.2512072345220.49654@angie.orcam.me.uk/__;!!ACWV5N9M2RV99hQ!OAfq9yiKnpdaetDotJN22sQQSGBYwwgga65vyQgENCufGjXofXKzxK_fIlCshhI-_EDkeOuLzjgvx4I5zng$ >.
> Re-verified with 6.19.0-rc7.
> 
>    Maciej

We’re waiting on this patch. Are there any updates or plans for it?

Thanks,
Alok

  reply	other threads:[~2026-02-19  3:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 19:24 [PATCH " Maciej W. Rozycki
2025-12-08 19:24 ` [PATCH v2 1/3] " Maciej W. Rozycki
2026-02-05 11:00   ` [External] : " ALOK TIWARI
2025-12-08 19:24 ` [PATCH v2 2/3] PCI: Use pcie_get_speed_cap() " Maciej W. Rozycki
2026-02-05 10:59   ` [External] : " ALOK TIWARI
2025-12-08 19:24 ` [PATCH v2 3/3] PCI: Bail out early for 2.5GT/s devices " Maciej W. Rozycki
2026-02-05 10:57   ` [External] : " ALOK TIWARI
2026-02-04 17:12 ` [PING][PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction " Maciej W. Rozycki
2026-02-19  3:42   ` ALOK TIWARI [this message]
2026-03-09 15:45     ` ALOK TIWARI
2026-02-19 21:26 ` [PATCH " Bjorn Helgaas
2026-02-19 22:09   ` [PATCH] " Matthew W Carlis
2026-02-19 22:53     ` Bjorn Helgaas
2026-02-20 12:03       ` Maciej W. Rozycki
2026-02-23 17:36         ` Bjorn Helgaas
2026-02-23 22:49           ` Matthew W Carlis
2026-02-23 23:14           ` Maciej W. Rozycki
2026-02-25  1:41             ` Matthew W Carlis
2026-02-26 22:02               ` Maciej W. Rozycki
2026-03-26 19:52                 ` ALOK TIWARI
2026-04-30 15:27                   ` ALOK TIWARI
2026-05-06 22:30 ` [PATCH v2 0/3] " 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=d6d04a8f-5845-4627-8cf1-a6875cb21fbb@oracle.com \
    --to=alok.a.tiwari@oracle.com \
    --cc=ahuang12@lenovo.com \
    --cc=ashishk@purestorage.com \
    --cc=bhelgaas@google.com \
    --cc=guojinhui.liam@bytedance.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jiwei.sun.bj@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=macro@orcam.me.uk \
    --cc=mattc@purestorage.com \
    --cc=msaggi@purestorage.com \
    --cc=sconnor@purestorage.com \
    --cc=sunjw10@lenovo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®