[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165692821434.21895.12215940507809769729.git-patchwork-notify@kernel.org>
Date: Mon, 04 Jul 2022 09:50:14 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Lukas Wunner <lukas@...ner.de>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, netdev@...r.kernel.org,
linux-usb@...r.kernel.org, steve.glendinning@...well.net,
UNGLinuxDriver@...rochip.com, oneukum@...e.com,
andre.edich@...rochip.com, o.rempel@...gutronix.de,
linux@...pel-privat.de, martyn.welch@...labora.com,
ghojda@...urs.ro, chf.fritz@...glemail.com, LinoSanfilippo@....de,
p.rosenberger@...bus.com, m.szyprowski@...sung.com,
fntoth@...il.com, andrew@...n.ch, stern@...land.harvard.edu
Subject: Re: [PATCH net-next v2 0/3] Deadlock no more in LAN95xx
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:
On Fri, 1 Jul 2022 22:47:50 +0200 you wrote:
> Second attempt at fixing a runtime resume deadlock in the LAN95xx USB driver:
>
> In short, the driver isn't using the "nopm" register accessors in portions
> of its runtime resume path, causing a deadlock. I'm fixing that by
> auto-detecting whether nopm accessors shall be used, instead of
> having to explicitly call them wherever it's necessary.
> As a byproduct, code size shrinks significantly (see diffstat below).
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] usbnet: smsc95xx: Fix deadlock on runtime resume
https://git.kernel.org/netdev/net-next/c/7b960c967f2a
- [net-next,v2,2/3] usbnet: smsc95xx: Clean up nopm handling
https://git.kernel.org/netdev/net-next/c/3147242980c5
- [net-next,v2,3/3] usbnet: smsc95xx: Clean up unnecessary BUG_ON() upon register access
https://git.kernel.org/netdev/net-next/c/03b3df43ce1f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists