From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: M M <restafvalendergelijke@outlook.com>,
"armando.araujo@syncnow.net" <armando.araujo@syncnow.net>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@leemhuis.info" <regressions@leemhuis.info>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link
Date: Fri, 9 Oct 2026 13:36:02 +0200 [thread overview]
Message-ID: <19cdc3df-fcdc-405d-be05-d018b09932d9@proxmox.com> (raw)
In-Reply-To: <DU2PPFBE35756D171CD64356C8D8DF3C2F8AB922@DU2PPFBE35756D1.EURP189.PROD.OUTLOOK.COM>
On 09/10/2026 12:53, M M wrote:
> Thank you Armando for the detailed follow-up. It's "good" to see this problem is still active, though Proxmox is really slow with this. In the meantime we are 1,5 month ahead and without the much needed security updates related to the kernel.
> I can only hope there will be some progress soon on their behalf, but it's pretty much quiet at Proxmox in general.
Please stop CC'ing random people and Proxmox email addresses that half
not even exist, that's just spamming, please stop that. Also not sure
what your talking w.r.t. security updates, we release fixes in our kernel
on a steady stream and are up-to-date here.
Besides, our downstream info about this was that one user tried the patch
and it did not work for them and you could not confirm this either as
requested in the same reply telling you [0], so we did not look at this
at all due to waiting on feedback. btw. did you actually test this now
confirming it fixes the issues on your system?
As v3 on its own would leave most of our reports broken, revert is more
likely to help here for the broader masses and will be the route we
look into.
[0]: https://bugzilla.proxmox.com/show_bug.cgi?id=7969#c8
next prev parent reply other threads:[~2026-10-09 11:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DU2PPFBE35756D171CD64356C8D8DF3C2F8AB922@DU2PPFBE35756D1.EURP189.PROD.OUTLOOK.COM>
2026-10-09 11:21 ` M M
2026-10-09 11:36 ` Thomas Lamprecht [this message]
2026-10-07 14:03 SyncNOW.net - Armando Araujo Filho
-- strict thread matches above, loose matches on Subject: below --
2026-09-20 8:15 blaat windows
2026-08-01 20:11 Andreas Wild
2026-08-03 5:39 ` Thorsten Leemhuis
2026-08-03 22:07 ` Maciej W. Rozycki
2026-08-04 5:32 ` Thorsten Leemhuis
2026-08-07 19:59 ` Aoxtj
2026-08-08 6:31 ` Andreas Wild
2026-08-11 3:43 ` Aoxtj
2026-08-11 6:42 ` Andreas Wild
2026-08-24 14:26 ` Thorsten Leemhuis
2026-08-25 7:05 ` Andreas Wild
2026-08-25 10:18 ` Maciej W. Rozycki
2026-09-02 15:48 ` Thorsten Leemhuis
2026-09-07 12:33 ` Maciej W. Rozycki
2026-09-17 23:33 ` Bjorn Helgaas
2026-09-18 5:39 ` Thorsten Leemhuis
2026-09-18 10:39 ` Maciej W. Rozycki
2026-09-18 11:00 ` Thorsten Leemhuis
2026-09-18 12:18 ` Maciej W. Rozycki
2026-09-18 12:50 ` Thorsten Leemhuis
2026-09-21 10:33 ` Thorsten Leemhuis
2026-09-29 5:45 ` Thorsten Leemhuis
2026-09-29 7:59 ` Andreas Wild
2026-10-21 2:23 ` Edward Malik
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=19cdc3df-fcdc-405d-be05-d018b09932d9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=armando.araujo@syncnow.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=restafvalendergelijke@outlook.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®