From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, leonro@nvidia.com,
idosch@nvidia.com, mingo@redhat.com, jiri@nvidia.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mlxsw@nvidia.com, moshe@nvidia.com, netdev@vger.kernel.org,
saeedm@nvidia.com, salil.mehta@huawei.com, shayd@nvidia.com,
rostedt@goodmis.org, tariqt@nvidia.com, yisen.zhuang@huawei.com
Subject: Re: [PATCH net-next v4 0/6] devlink reload simplification
Date: Wed, 13 Oct 2021 00:20:07 +0000 [thread overview]
Message-ID: <163408440777.9622.8852746022639059437.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1634044267.git.leonro@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 Oct 2021 16:15:20 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v4:
> * Removed legacy BUG_ON() in first patch.
> * Added new patch that moves netdev_to_devlink functions to devlink.c.
> * Rewrote devlink ops patch to use feature mask.
> v3: https://lore.kernel.org/all/cover.1633589385.git.leonro@nvidia.com
> * Rewrote third patch to keep static const nature of ops. This is done
> by extracting reload ops to separate ops structure.
> * Changed commit message in last patch as was suggested by Ido.
> v2: https://lore.kernel.org/all/cover.1633284302.git.leonro@nvidia.com
> * Dropped const removal patch
> * Added new patch to hide struct devlink
> * Added new patch to annotate devlink API
> * Implemented copy of all callback in devlink ops
> v1: https://lore.kernel.org/all/cover.1632916329.git.leonro@nvidia.com
> * Missed removal of extra WARN_ON
> * Added "ops parameter to macro as Dan suggested.
> v0: https://lore.kernel.org/all/cover.1632909221.git.leonro@nvidia.com
>
> [...]
Here is the summary with links:
- [net-next,v4,1/6] devlink: Reduce struct devlink exposure
https://git.kernel.org/netdev/net-next/c/21314638c9f2
- [net-next,v4,2/6] devlink: Move netdev_to_devlink helpers to devlink.c
https://git.kernel.org/netdev/net-next/c/2bc50987dc1f
- [net-next,v4,3/6] devlink: Annotate devlink API calls
https://git.kernel.org/netdev/net-next/c/b88f7b1203bf
- [net-next,v4,4/6] devlink: Allow control devlink ops behavior through feature mask
https://git.kernel.org/netdev/net-next/c/bd032e35c568
- [net-next,v4,5/6] net/mlx5: Set devlink reload feature bit for supported devices only
https://git.kernel.org/netdev/net-next/c/96869f193cfd
- [net-next,v4,6/6] devlink: Delete reload enable/disable interface
https://git.kernel.org/netdev/net-next/c/82465bec3e97
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:[~2021-10-13 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:15 [PATCH net-next v4 0/6] devlink reload simplification Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 1/6] devlink: Reduce struct devlink exposure Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 2/6] devlink: Move netdev_to_devlink helpers to devlink.c Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 3/6] devlink: Annotate devlink API calls Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 4/6] devlink: Allow control devlink ops behavior through feature mask Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 5/6] net/mlx5: Set devlink reload feature bit for supported devices only Leon Romanovsky
2021-10-12 13:15 ` [PATCH net-next v4 6/6] devlink: Delete reload enable/disable interface Leon Romanovsky
2021-10-13 0:20 ` 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=163408440777.9622.8852746022639059437.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=saeedm@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.