From: patchwork-bot+netdevbpf@kernel.org
To: Jun Gu <jun.gu@easystack.cn>
Cc: kuba@kernel.org, dev@openvswitch.org, echaudro@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4] net: openvswitch: Check vport netdev name
Date: Tue, 23 Apr 2024 00:53:13 +0000 [thread overview]
Message-ID: <171383359326.888.13888365366178686900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240419061425.132723-1-jun.gu@easystack.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 19 Apr 2024 14:14:25 +0800 you wrote:
> Ensure that the provided netdev name is not one of its aliases to
> prevent unnecessary creation and destruction of the vport by
> ovs-vswitchd.
>
> Signed-off-by: Jun Gu <jun.gu@easystack.cn>
> Acked-by: Eelco Chaudron <echaudro@redhat.com>
>
> [...]
Here is the summary with links:
- [net-next,v4] net: openvswitch: Check vport netdev name
https://git.kernel.org/netdev/net-next/c/2540088b836f
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:[~2024-04-23 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 6:14 [PATCH net-next v4] net: openvswitch: Check vport netdev name Jun Gu
2024-04-23 0:38 ` Jakub Kicinski
2024-04-23 2:34 ` Jun Gu
2024-04-23 0:53 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-17 10:48 [PATCH net-next v3] net: openvswitch: Check vport net device name Eelco Chaudron
2024-04-18 2:32 ` [PATCH net-next v4] net: openvswitch: Check vport netdev name jun.gu
2024-04-18 15:38 ` Jakub Kicinski
2024-04-19 4:31 ` Jun Gu
2024-04-20 3:01 ` 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=171383359326.888.13888365366178686900.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=jun.gu@easystack.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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