From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, "Andrew Lunn" <andrew@lunn.ch>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
linux-arm-kernel@lists.infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Simon Horman" <horms@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>,
"Stanislav Fomichev" <sdf@fomichev.me>
Subject: Re: [PATCH net-next 0/7] net: ethtool: Introduce ethnl dump helpers
Date: Wed, 5 Mar 2025 18:47:49 -0800 [thread overview]
Message-ID: <20250305184749.5519e7a9@kernel.org> (raw)
In-Reply-To: <20250305180252.5a0ceb86@fedora.home>
On Wed, 5 Mar 2025 18:02:52 +0100 Maxime Chevallier wrote:
> This series will very likely conflict with Stanislav's netdev lock
> work [2], I'll of course be happy to rebase should it get merged :)
Also this doesn't build. Please hold off on reposting for a couple of
days - because of the large conflict radius the previous few revisions
of the locking series haven't even gotten into the selftest CI queue :(
next prev parent reply other threads:[~2025-03-06 2:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 14:19 [PATCH net-next 0/7] net: ethtool: Introduce ethnl dump helpers Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 1/7] net: ethtool: netlink: Allow per-netdevice DUMP operations Maxime Chevallier
2025-03-07 12:21 ` Simon Horman
2025-03-07 13:18 ` Maxime Chevallier
2025-03-07 15:14 ` Simon Horman
2025-03-05 14:19 ` [PATCH net-next 2/7] net: ethtool: netlink: Rename ethnl_default_dump_one Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 3/7] net: ethtool: netlink: Introduce command-specific dump_one_dev Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 4/7] net: ethtool: netlink: Introduce per-phy DUMP helpers Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 5/7] net: ethtool: phy: Convert the PHY_GET command to generic phy dump Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 6/7] net: ethtool: plca: Use per-PHY DUMP operations Maxime Chevallier
2025-03-05 14:19 ` [PATCH net-next 7/7] net: ethtool: pse-pd: " Maxime Chevallier
2025-03-05 17:02 ` [PATCH net-next 0/7] net: ethtool: Introduce ethnl dump helpers Maxime Chevallier
2025-03-06 2:47 ` Jakub Kicinski [this message]
2025-03-06 7:42 ` Maxime Chevallier
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=20250305184749.5519e7a9@kernel.org \
--to=kuba@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=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=sdf@fomichev.me \
--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).