From: patchwork-bot+netdevbpf@kernel.org
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, rmk+kernel@armlinux.org.uk,
hkallweit1@gmail.com, f.fainelli@gmail.com
Subject: Re: [PATCH net-next 0/2] Add additional phydev locks
Date: Mon, 20 Feb 2023 10:10:16 +0000 [thread overview]
Message-ID: <167688781696.25409.9806793382078281550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230217030714.1249009-1-andrew@lunn.ch>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.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
prev parent reply other threads:[~2023-02-20 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 3:07 [PATCH net-next 0/2] Add additional phydev locks Andrew Lunn
2023-02-17 3:07 ` [=PATCH net-next 1/2] net: phy: marvell: Use the unlocked genphy_c45_ethtool_get_eee() Andrew Lunn
2023-02-17 3:07 ` [=PATCH net-next 2/2] net: phy: Add locks to ethtool functions Andrew Lunn
2023-02-20 10:10 ` 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=167688781696.25409.9806793382078281550.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).