From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: kuba@kernel.org, jiri@nvidia.com, davem@davemloft.net,
leonro@nvidia.com, netdev@vger.kernel.org, saeedm@nvidia.com,
vigneshr@ti.com
Subject: Re: [PATCH net-next v1 0/3] Remove duplicated devlink registration check
Date: Wed, 28 Jul 2021 09:30:06 +0000 [thread overview]
Message-ID: <162746460645.7734.12377729175647857455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1627456849.git.leonro@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 28 Jul 2021 10:33:44 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Changelog:
> v1:
> * Added two new patches that remove registration field from mlx5 and ti drivers.
> v0: https://lore.kernel.org/lkml/ed7bbb1e4c51dd58e6035a058e93d16f883b09ce.1627215829.git.leonro@nvidia.com
>
> [...]
Here is the summary with links:
- [net-next,v1,1/3] net: ti: am65-cpsw-nuss: fix wrong devlink release order
https://git.kernel.org/netdev/net-next/c/acf34954efd1
- [net-next,v1,2/3] net/mlx5: Don't rely on always true registered field
https://git.kernel.org/netdev/net-next/c/35f6986743d7
- [net-next,v1,3/3] devlink: Remove duplicated registration check
https://git.kernel.org/netdev/net-next/c/d7907a2b1a3b
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-28 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 7:33 [PATCH net-next v1 0/3] Remove duplicated devlink registration check Leon Romanovsky
2021-07-28 7:33 ` [PATCH net-next v1 1/3] net: ti: am65-cpsw-nuss: fix wrong devlink release order Leon Romanovsky
2021-07-28 7:33 ` [PATCH net-next v1 2/3] net/mlx5: Don't rely on always true registered field Leon Romanovsky
2021-07-28 7:33 ` [PATCH net-next v1 3/3] devlink: Remove duplicated registration check Leon Romanovsky
2021-07-28 9: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=162746460645.7734.12377729175647857455.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=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=vigneshr@ti.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.