Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH RESEND net-next 00/10] devlink: Control auxiliary devices
Date: Wed, 11 Aug 2021 13:40:07 +0000 [thread overview]
Message-ID: <162868920724.16245.8369444403907708271.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210810132424.9129-1-parav@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 10 Aug 2021 16:24:14 +0300 you wrote:
> (Resend to CC RDMA and vdpa mailing lists).
>
> Hi Dave, Jakub,
>
> Currently, for mlx5 multi-function device, a user is not able to control
> which functionality to enable/disable. For example, each PCI
> PF, VF, SF function by default has netdevice, RDMA and vdpa-net
> devices always enabled.
>
> [...]
Here is the summary with links:
- [RESEND,net-next,01/10] devlink: Add new "enable_eth" generic device param
https://git.kernel.org/netdev/net-next/c/f13a5ad88186
- [RESEND,net-next,02/10] devlink: Add new "enable_rdma" generic device param
https://git.kernel.org/netdev/net-next/c/8ddaabee3c79
- [RESEND,net-next,03/10] devlink: Add new "enable_vnet" generic device param
https://git.kernel.org/netdev/net-next/c/076b2a9dbb28
- [RESEND,net-next,04/10] devlink: Create a helper function for one parameter registration
https://git.kernel.org/netdev/net-next/c/699784f7b728
- [RESEND,net-next,05/10] devlink: Add API to register and unregister single parameter
https://git.kernel.org/netdev/net-next/c/b40c51efefbc
- [RESEND,net-next,06/10] devlink: Add APIs to publish, unpublish individual parameter
https://git.kernel.org/netdev/net-next/c/9c4a7665b423
- [RESEND,net-next,07/10] net/mlx5: Fix unpublish devlink parameters
https://git.kernel.org/netdev/net-next/c/6f35723864b4
- [RESEND,net-next,08/10] net/mlx5: Support enable_eth devlink dev param
https://git.kernel.org/netdev/net-next/c/a17beb28ed9d
- [RESEND,net-next,09/10] net/mlx5: Support enable_rdma devlink dev param
https://git.kernel.org/netdev/net-next/c/87158cedf00e
- [RESEND,net-next,10/10] net/mlx5: Support enable_vnet devlink dev param
https://git.kernel.org/netdev/net-next/c/70862a5d609d
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-08-11 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 13:24 Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 01/10] devlink: Add new "enable_eth" generic device param Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 02/10] devlink: Add new "enable_rdma" " Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 03/10] devlink: Add new "enable_vnet" " Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 04/10] devlink: Create a helper function for one parameter registration Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 05/10] devlink: Add API to register and unregister single parameter Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 06/10] devlink: Add APIs to publish, unpublish individual parameter Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 07/10] net/mlx5: Fix unpublish devlink parameters Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 08/10] net/mlx5: Support enable_eth devlink dev param Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 09/10] net/mlx5: Support enable_rdma " Parav Pandit
2021-08-10 13:24 ` [PATCH RESEND net-next 10/10] net/mlx5: Support enable_vnet " Parav Pandit
2021-08-11 13: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=162868920724.16245.8369444403907708271.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
--subject='Re: [PATCH RESEND net-next 00/10] devlink: Control auxiliary devices' \
/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
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).