[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167688781696.25409.9806793382078281550.git-patchwork-notify@kernel.org>
Date: Mon, 20 Feb 2023 10:10:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, rmk+kernel@...linux.org.uk,
hkallweit1@...il.com, f.fainelli@...il.com
Subject: Re: [PATCH net-next 0/2] Add additional phydev locks
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:
On Fri, 17 Feb 2023 04:07:12 +0100 you wrote:
> The phydev lock should be held when accessing members of phydev, or
> calling into the driver. Some of the phy_ethtool_ functions are
> missing locks. Add them. To avoid deadlock the marvell driver is
> modified since it calls one of the functions which gain locks, which
> would result in a deadlock.
>
> The missing locks have not caused noticeable issues, so these patches
> are for net-next.
>
> [...]
Here is the summary with links:
- [=PATCH,net-next,1/2] net: phy: marvell: Use the unlocked genphy_c45_ethtool_get_eee()
https://git.kernel.org/netdev/net-next/c/3365777a6a22
- [=PATCH,net-next,2/2] net: phy: Add locks to ethtool functions
https://git.kernel.org/netdev/net-next/c/2f987d486610
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