Received-SPF: pass (google.com: domain of linux-kernel+bounces-199945-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH REPOST net-next 1/2] r8152: If inaccessible at resume time,
 issue a reset
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171746643321.10384.14422859264596064414.git-patchwork-notify@kernel.org>
Date: Tue, 04 Jun 2024 02:00:33 +0000
References: <66590f22.170a0220.8b5ad.1750@mx.google.com>
In-Reply-To: <66590f22.170a0220.8b5ad.1750@mx.google.com>
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

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