From: Heiner Kallweit <hkallweit1@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: amd-gfx@lists.freedesktop.org, Alexander.Deucher@amd.com,
mario.limonciello@amd.com, yifan1.zhang@amd.com,
stable@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Li Ma <li.ma@amd.com>
Subject: Re: [PATCH] r8169: fix ASPM-related issues on a number of systems with NIC version from RTL8168h
Date: Wed, 8 Nov 2023 08:40:48 +0100 [thread overview]
Message-ID: <9a5ba6df-5d15-4c23-98cd-686b1f62e05b@gmail.com> (raw)
In-Reply-To: <2023110845-factual-dawn-7d68@gregkh>
On 08.11.2023 08:05, Greg KH wrote:
> On Wed, Nov 08, 2023 at 11:34:00AM +0800, Li Ma wrote:
>> From: Heiner Kallweit <hkallweit1@gmail.com>
>>
>> This effectively reverts 4b5f82f6aaef. On a number of systems ASPM L1
>> causes tx timeouts with RTL8168h, see referenced bug report.
>>
>> Fixes: 4b5f82f6aaef ("r8169: enable ASPM L1/L1.1 from RTL8168h")
>> Cc: stable@vger.kernel.org
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217814
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>> (cherry picked from commit 90ca51e8c654699b672ba61aeaa418dfb3252e5e)
>> ---
>> drivers/net/ethernet/realtek/r8169_main.c | 4 ----
>> 1 file changed, 4 deletions(-)
>
> Is this a proposed stable tree patch? If so, what kernel(s) are you
> wanting it applied to?
>
This should have been sent neither to you nor stable@vger.kernel.org.
This patch has been applied to stable already, the mail is something
AMD-internal it seems.
> thanks,
>
> greg k-h
Heiner
next prev parent reply other threads:[~2023-11-08 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 3:34 [PATCH] r8169: fix ASPM-related issues on a number of systems with NIC version from RTL8168h Li Ma
2023-11-08 7:05 ` Greg KH
2023-11-08 7:40 ` Heiner Kallweit [this message]
2023-11-08 7:52 ` Greg KH
2023-11-08 8:11 ` Ma, Li
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 8:52 Li Ma
2023-11-07 18:17 ` Mario Limonciello
2023-11-08 2:31 ` Ma, Li
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=9a5ba6df-5d15-4c23-98cd-686b1f62e05b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=li.ma@amd.com \
--cc=mario.limonciello@amd.com \
--cc=stable@vger.kernel.org \
--cc=yifan1.zhang@amd.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