From: patchwork-bot+netdevbpf@kernel.org
To: Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
Cc: jiri@nvidia.com, netdev@vger.kernel.org, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, bbrezillon@kernel.org,
arno@natisbad.org, schalla@marvell.com, kurt@linutronix.de,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
michael.chan@broadcom.com, ioana.ciornei@nxp.com,
dmichail@fungible.com, yisen.zhuang@huawei.com,
salil.mehta@huawei.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, sgoutham@marvell.com,
lcherian@marvell.com, gakula@marvell.com, jerinj@marvell.com,
hkelam@marvell.com, sbhatta@marvell.com, tchornyi@marvell.com,
saeedm@nvidia.com, leon@kernel.org, idosch@nvidia.com,
petrm@nvidia.com, simon.horman@corigine.com, snelson@pensando.io,
drivers@pensando.io, aelior@marvell.com, manishc@marvell.com,
jonathan.lemon@gmail.com, vadfed@fb.com,
richardcochran@gmail.com, vadimp@mellanox.com,
shalomt@mellanox.com, linux-crypto@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
oss-drivers@corigine.com, jiri@mellanox.com,
herbert@gondor.apana.org.au, chenhao288@hisilicon.com,
huangguangbin2@huawei.com, chi.minghao@zte.com.cn,
sthotton@marvell.com
Subject: Re: [PATCH net-next v6 0/3] net: devlink: return the driver name in devlink_nl_info_fill
Date: Thu, 01 Dec 2022 06:10:17 +0000 [thread overview]
Message-ID: <166987501717.18933.6140637869420910519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221129095140.3913303-1-mailhol.vincent@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Nov 2022 18:51:37 +0900 you wrote:
> The driver name is available in device_driver::name. Right now,
> drivers still have to report this piece of information themselves in
> their devlink_ops::info_get callback function.
>
> The goal of this series is to have the devlink core to report this
> information instead of the drivers.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/3] net: devlink: let the core report the driver name instead of the drivers
https://git.kernel.org/netdev/net-next/c/226bf9805506
- [net-next,v6,2/3] net: devlink: make the devlink_ops::info_get() callback optional
https://git.kernel.org/netdev/net-next/c/c5cd7c86847c
- [net-next,v6,3/3] net: devlink: clean-up empty devlink_ops::info_get()
https://git.kernel.org/netdev/net-next/c/cf4590b91db4
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:[~2022-12-01 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:51 [PATCH net-next v6 0/3] net: devlink: return the driver name in devlink_nl_info_fill Vincent Mailhol
2022-11-29 9:51 ` [PATCH net-next v6 1/3] net: devlink: let the core report the driver name instead of the drivers Vincent Mailhol
2022-11-29 9:51 ` [PATCH net-next v6 2/3] net: devlink: make the devlink_ops::info_get() callback optional Vincent Mailhol
2022-11-29 9:51 ` [PATCH net-next v6 3/3] net: devlink: clean-up empty devlink_ops::info_get() Vincent Mailhol
2022-12-01 6: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=166987501717.18933.6140637869420910519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=chi.minghao@zte.com.cn \
--cc=davem@davemloft.net \
--cc=dmichail@fungible.com \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gakula@marvell.com \
--cc=herbert@gondor.apana.org.au \
--cc=hkelam@marvell.com \
--cc=huangguangbin2@huawei.com \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ioana.ciornei@nxp.com \
--cc=jerinj@marvell.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@mellanox.com \
--cc=jiri@nvidia.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=lcherian@marvell.com \
--cc=leon@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@marvell.com \
--cc=shalomt@mellanox.com \
--cc=simon.horman@corigine.com \
--cc=snelson@pensando.io \
--cc=sthotton@marvell.com \
--cc=tchornyi@marvell.com \
--cc=vadfed@fb.com \
--cc=vadimp@mellanox.com \
--cc=yisen.zhuang@huawei.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