[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fff3067d-5a7f-b328-ef65-fa68138f8b0f@leemhuis.info>
Date: Fri, 14 Jul 2023 08:30:03 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Heiner Kallweit <hkallweit1@...il.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
Jakub Kicinski <kuba@...nel.org>, David Miller <davem@...emloft.net>,
Realtek linux nic maintainers <nic_swsd@...ltek.com>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, joey.joey586@...il.com
Subject: Re: [PATCH net] r8169: fix ASPM-related problem for chip version 42
and 43
On 14.07.23 07:34, Heiner Kallweit wrote:
> On 14.07.2023 05:31, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 13.07.23 21:46, Heiner Kallweit wrote:
>
>>> Fixes: 5fc3f6c90cca ("r8169: consolidate disabling ASPM before EPHY access")
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217635 # [0]
>> A "Cc: stable@...r.kernel.org" would be nice, too, to get this fixed in
>> 6.4, where this surfaced (reminder: no, a Fixes: tag is not enough to
>> ensure the backport there).
> That's different in the net subsystem. The net (vs. net-next) annotation
> ensures the backport.
Huh, how does that work? I thought "net" currently means "for 6.5" while
"net-next" implies 6.6?
Ciao, Thorsten
Powered by blists - more mailing lists