From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, leonro@nvidia.com,
alexandre.belloni@bootlin.com, andrew@lunn.ch,
aelior@marvell.com, luobin9@huawei.com, claudiu.manoil@nxp.com,
coiby.xu@gmail.com, dchickles@marvell.com, drivers@pensando.io,
fmanlunas@marvell.com, f.fainelli@gmail.com, gakula@marvell.com,
gregkh@linuxfoundation.org, GR-everest-linux-l2@marvell.com,
GR-Linux-NIC-Dev@marvell.com, hkelam@marvell.com,
idosch@nvidia.com, linuxwwan@intel.com,
intel-wired-lan@lists.osuosl.org, ioana.ciornei@nxp.com,
jerinj@marvell.com, jesse.brandeburg@intel.com, jiri@nvidia.com,
jonathan.lemon@gmail.com, lcherian@marvell.com,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-staging@lists.linux.dev,
loic.poulain@linaro.org, manishc@marvell.com,
m.chetan.kumar@intel.com, michael.chan@broadcom.com,
netdev@vger.kernel.org, oss-drivers@corigine.com,
richardcochran@gmail.com, saeedm@nvidia.com,
salil.mehta@huawei.com, sburla@marvell.com,
ryazanov.s.a@gmail.com, snelson@pensando.io,
simon.horman@corigine.com, sbhatta@marvell.com,
sgoutham@marvell.com, tchornyi@marvell.com, tariqt@nvidia.com,
anthony.l.nguyen@intel.com, UNGLinuxDriver@microchip.com,
vkochan@marvell.com, vivien.didelot@gmail.com,
vladimir.oltean@nxp.com, yisen.zhuang@huawei.com
Subject: Re: [PATCH net-next v1] devlink: Make devlink_register to be void
Date: Wed, 22 Sep 2021 13:20:07 +0000 [thread overview]
Message-ID: <163231680725.16453.13582291901349669974.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <311a6c7e74ad612474446890a12c9d310b9507ed.1632300324.git.leonro@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 22 Sep 2021 11:58:03 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> devlink_register() can't fail and always returns success, but all drivers
> are obligated to check returned status anyway. This adds a lot of boilerplate
> code to handle impossible flow.
>
> Make devlink_register() void and simplify the drivers that use that
> API call.
>
> [...]
Here is the summary with links:
- [net-next,v1] devlink: Make devlink_register to be void
https://git.kernel.org/netdev/net-next/c/db4278c55fa5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-09-22 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 8:58 [PATCH net-next v1] devlink: Make devlink_register to be void Leon Romanovsky
2021-09-22 12:01 ` Simon Horman
2021-09-22 12:05 ` Vladimir Oltean
2021-09-22 12:15 ` Jiri Pirko
2021-09-22 13:20 ` patchwork-bot+netdevbpf [this message]
2021-09-22 13:22 ` Jakub Kicinski
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=163231680725.16453.13582291901349669974.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=GR-everest-linux-l2@marvell.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=aelior@marvell.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=claudiu.manoil@nxp.com \
--cc=coiby.xu@gmail.com \
--cc=davem@davemloft.net \
--cc=dchickles@marvell.com \
--cc=drivers@pensando.io \
--cc=f.fainelli@gmail.com \
--cc=fmanlunas@marvell.com \
--cc=gakula@marvell.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkelam@marvell.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@nvidia.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=luobin9@huawei.com \
--cc=m.chetan.kumar@intel.com \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=richardcochran@gmail.com \
--cc=ryazanov.s.a@gmail.com \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=sbhatta@marvell.com \
--cc=sburla@marvell.com \
--cc=sgoutham@marvell.com \
--cc=simon.horman@corigine.com \
--cc=snelson@pensando.io \
--cc=tariqt@nvidia.com \
--cc=tchornyi@marvell.com \
--cc=vivien.didelot@gmail.com \
--cc=vkochan@marvell.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).