[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05d53fd2-f210-1963-96d1-2dc3d0a3a8c7@gmail.com>
Date: Sat, 28 Mar 2020 10:52:19 +0100
From: Heiner Kallweit <hkallweit1@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: David Miller <davem@...emloft.net>, nic_swsd@...ltek.com,
cwhuang@...roid-x86.org, netdev@...r.kernel.org
Subject: Re: issue with 85a19b0e31e2 on 4.19 -> revert
On 28.03.2020 00:24, David Miller wrote:
> From: Heiner Kallweit <hkallweit1@...il.com>
> Date: Sat, 28 Mar 2020 00:10:57 +0100
>
>> Somehow that change made it to -stable. See e.g. commit
>> 85a19b0e31e256e77fd4124804b9cec10619de5e for 4.19.
>
> This is a serious issue in that it seems that the people maintaining
> the older stable release integrate arbitrary patches even if they
> haven't been sent to v5.4 and v5.5
>
> And I don't handle -stable backport submissions that far back anyways.
>
> Therefore, I'm not going to participate in that ongoing problem, so
> feel free to contact the folks who integrated those changes into
> -stable and ask them to revert.
>
> Thanks.
>
Greg,
commit 85a19b0e31e2 ("r8169: check that Realtek PHY driver module is loaded")
made it accidentally to 4.19 and causes an issue with Android/x86.
Could you please revert it?
Thanks, Heiner
Powered by blists - more mailing lists