From: patchwork-bot+netdevbpf@kernel.org
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, andrew@lunn.ch, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, hkallweit1@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
linux-arm-kernel@lists.infradead.org,
christophe.leroy@csgroup.eu, herve.codina@bootlin.com,
f.fainelli@gmail.com, linux@armlinux.org.uk,
vladimir.oltean@nxp.com, kory.maincent@bootlin.com,
o.rempel@pengutronix.de, horms@kernel.org,
romain.gantois@bootlin.com, piergiorgio.beruto@gmail.com
Subject: Re: [PATCH net-next v8 0/3] net: ethtool: Introduce ethnl dump helpers
Date: Tue, 06 May 2025 01:40:34 +0000 [thread overview]
Message-ID: <174649563473.1007977.7672899969747094787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250502085242.248645-1-maxime.chevallier@bootlin.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 May 2025 10:52:38 +0200 you wrote:
> Hi everyone,
>
> This is V8 for per-phy DUMP helpers, improving support for ->dumpit()
> operations for PHY targetting commands.
>
> This V8 fixes some issues spotted by Jakub (thanks !) on the multi-part
> DUMP sequence. The netdev reftracking was reworked to make sure that
> during a filtered DUMP, we only keep a ref on the netdev during
> individual .dumpit() calls.
>
> [...]
Here is the summary with links:
- [net-next,v8,1/3] net: ethtool: Introduce per-PHY DUMP operations
https://git.kernel.org/netdev/net-next/c/172265b44cd3
- [net-next,v8,2/3] net: ethtool: phy: Convert the PHY_GET command to generic phy dump
https://git.kernel.org/netdev/net-next/c/9dd2ad5e92b9
- [net-next,v8,3/3] net: ethtool: netlink: Use netdev_hold for dumpit() operations
https://git.kernel.org/netdev/net-next/c/63fb100bf524
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:[~2025-05-06 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 8:52 [PATCH net-next v8 0/3] net: ethtool: Introduce ethnl dump helpers Maxime Chevallier
2025-05-02 8:52 ` [PATCH net-next v8 1/3] net: ethtool: Introduce per-PHY DUMP operations Maxime Chevallier
2025-05-02 8:52 ` [PATCH net-next v8 2/3] net: ethtool: phy: Convert the PHY_GET command to generic phy dump Maxime Chevallier
2025-05-02 8:52 ` [PATCH net-next v8 3/3] net: ethtool: netlink: Use netdev_hold for dumpit() operations Maxime Chevallier
2025-05-06 1:40 ` 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=174649563473.1007977.7672899969747094787.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).