From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
leonro@nvidia.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, parav@nvidia.com
Subject: Re: [PATCH net-next v2 0/2] Clean devlink net namespace operations
Date: Fri, 30 Jul 2021 20:30:05 +0000 [thread overview]
Message-ID: <162767700561.11153.17362580046562666251.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1627578998.git.leonro@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 29 Jul 2021 20:19:23 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v2:
> * Patch 1: Dropped cmd argument
> v1: https://lore.kernel.org/lkml/cover.1627564383.git.leonro@nvidia.com
> * Patch 1:
> * Renamed function name
> * Added bool parameter to the notifier function
> * Patch 2:
> * added Jiri's ROB and dropped word "RAW" from the comment"
> v0: https://lore.kernel.org/lkml/cover.1627545799.git.leonro@nvidia.com
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] devlink: Break parameter notification sequence to be before/after unload/load driver
https://git.kernel.org/netdev/net-next/c/05a7f4a8dff1
- [net-next,v2,2/2] devlink: Allocate devlink directly in requested net namespace
https://git.kernel.org/netdev/net-next/c/26713455048e
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-07-30 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 17:19 [PATCH net-next v2 0/2] Clean devlink net namespace operations Leon Romanovsky
2021-07-29 17:19 ` [PATCH net-next v2 1/2] devlink: Break parameter notification sequence to be before/after unload/load driver Leon Romanovsky
2021-07-29 17:19 ` [PATCH net-next v2 2/2] devlink: Allocate devlink directly in requested net namespace Leon Romanovsky
2021-07-30 20:30 ` 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=162767700561.11153.17362580046562666251.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.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).