From: Florian Fainelli <f.fainelli@gmail.com>
To: patchwork-bot+netdevbpf@kernel.org,
Doug Anderson <dianders@chromium.org>
Cc: kuba@kernel.org, hayeswang@realtek.com, davem@davemloft.net,
ecgh@chromium.org, laura.nao@collabora.com,
stern@rowland.harvard.edu, horms@kernel.org,
linux-usb@vger.kernel.org, grundler@chromium.org, bjorn@mork.no,
edumazet@google.com, pabeni@redhat.com, pmalani@chromium.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v5 0/8] r8152: Avoid writing garbage to the adapter's registers
Date: Mon, 23 Oct 2023 18:27:13 -0700 [thread overview]
Message-ID: <acc63cea-5b51-4837-91ad-988d1a00e796@gmail.com> (raw)
In-Reply-To: <169797182424.5465.9720701078350268924.git-patchwork-notify@kernel.org>
On 10/22/2023 3:50 AM, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This series was applied to netdev/net.git (main)
> by David S. Miller <davem@davemloft.net>:
>
> On Fri, 20 Oct 2023 14:06:51 -0700 you wrote:
>> This series is the result of a cooperative debug effort between
>> Realtek and the ChromeOS team. On ChromeOS, we've noticed that Realtek
>> Ethernet adapters can sometimes get so wedged that even a reboot of
>> the host can't get them to enumerate again, assuming that the adapter
>> was on a powered hub and din't lose power when the host rebooted. This
>> is sometimes seen in the ChromeOS automated testing lab. The only way
>> to recover adapters in this state is to manually power cycle them.
>>
>> [...]
Oh well, late to the party, but this looks great, thanks!
--
Florian
prev parent reply other threads:[~2023-10-24 1:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 21:06 [PATCH v5 0/8] r8152: Avoid writing garbage to the adapter's registers Douglas Anderson
2023-10-20 21:06 ` [PATCH v5 1/8] r8152: Increase USB control msg timeout to 5000ms as per spec Douglas Anderson
2023-10-21 14:48 ` Grant Grundler
2023-10-24 1:23 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 2/8] r8152: Run the unload routine if we have errors during probe Douglas Anderson
2023-10-21 14:50 ` Grant Grundler
2023-10-24 1:24 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 3/8] r8152: Cancel hw_phy_work if we have an error in probe Douglas Anderson
2023-10-21 14:52 ` Grant Grundler
2023-10-24 1:24 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 4/8] r8152: Release firmware " Douglas Anderson
2023-10-21 15:01 ` Grant Grundler
2023-10-24 1:25 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 5/8] r8152: Check for unplug in rtl_phy_patch_request() Douglas Anderson
2023-10-21 15:03 ` Grant Grundler
2023-10-24 1:25 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 6/8] r8152: Check for unplug in r8153b_ups_en() / r8153c_ups_en() Douglas Anderson
2023-10-21 15:05 ` Grant Grundler
2023-10-24 1:25 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 7/8] r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE Douglas Anderson
2023-10-21 15:06 ` Grant Grundler
2023-10-24 1:26 ` Florian Fainelli
2023-10-20 21:06 ` [PATCH v5 8/8] r8152: Block future register access if register access fails Douglas Anderson
2023-10-21 15:35 ` Grant Grundler
2023-10-25 16:28 ` Simon Horman
2023-10-25 20:24 ` Doug Anderson
2023-11-03 16:52 ` Simon Horman
2023-10-22 10:50 ` [PATCH v5 0/8] r8152: Avoid writing garbage to the adapter's registers patchwork-bot+netdevbpf
2023-10-24 1:27 ` Florian Fainelli [this message]
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=acc63cea-5b51-4837-91ad-988d1a00e796@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=ecgh@chromium.org \
--cc=edumazet@google.com \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=pmalani@chromium.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).