From: patchwork-bot+netdevbpf@kernel.org
To: Doug Anderson <dianders@chromium.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, hayeswang@realtek.com,
danielgeorgem@google.com, andrew@lunn.ch, grundler@chromium.org,
hkallweit1@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH REPOST net-next 1/2] r8152: If inaccessible at resume time, issue a reset
Date: Tue, 04 Jun 2024 02:00:33 +0000 [thread overview]
Message-ID: <171746643321.10384.14422859264596064414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <66590f22.170a0220.8b5ad.1750@mx.google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 May 2024 16:43:08 -0700 you wrote:
> If we happened to get a USB transfer error during the transition to
> suspend then the usb_queue_reset_device() that r8152_control_msg()
> calls will get dropped on the floor. This is because
> usb_lock_device_for_reset() (which usb_queue_reset_device() uses)
> silently fails if it's called when a device is suspended or if too
> much time passes.
>
> [...]
Here is the summary with links:
- [REPOST,net-next,1/2] r8152: If inaccessible at resume time, issue a reset
https://git.kernel.org/netdev/net-next/c/4933b066fefb
- [REPOST,net-next,2/2] r8152: Wake up the system if the we need a reset
https://git.kernel.org/netdev/net-next/c/8c1d92a740c0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-06-04 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 23:43 [PATCH REPOST net-next 1/2] r8152: If inaccessible at resume time, issue a reset Douglas Anderson
2024-06-03 6:39 ` Hayes Wang
2024-06-04 2:00 ` patchwork-bot+netdevbpf [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=171746643321.10384.14422859264596064414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=danielgeorgem@google.com \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=edumazet@google.com \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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