From: Jakub Kicinski <kuba@kernel.org>
To: Jun Gu <jun.gu@easystack.cn>
Cc: 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: Fri, 19 Apr 2024 20:01:24 -0700 [thread overview]
Message-ID: <20240419200124.701cafb0@kernel.org> (raw)
In-Reply-To: <20240419043133.117295-1-jun.gu@easystack.cn>
On Fri, 19 Apr 2024 12:31:33 +0800 Jun Gu wrote:
> From: "jun.gu" <jun.gu@easystack.cn>
>
> 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>
I said: When you repost, start a new thread, do not post new version
in-reply-to.
If you don't understand what something means - ask :|
Now try again.
--
pw-bot: cr
next prev parent reply other threads:[~2024-04-20 3:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 8:48 [PATCH] net: openvswitch: Check vport name jun.gu
2024-04-15 10:04 ` [ovs-dev] " Eelco Chaudron
[not found] ` <671d3c3b-a5c4-4dbd-800b-fbfec0fbe4dc@easystack.cn>
2024-04-16 8:04 ` Eelco Chaudron
2024-04-16 9:20 ` [PATCH v2] net: openvswitch: Check vport net device name jun.gu
2024-04-16 11:19 ` Eelco Chaudron
2024-04-17 4:20 ` [PATCH net-next v3] " jun.gu
2024-04-17 10:48 ` 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
[not found] ` <20240419043133.117295-1-jun.gu@easystack.cn>
2024-04-20 3:01 ` Jakub Kicinski [this message]
2024-04-16 13:35 ` [PATCH] net: openvswitch: Check vport name Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
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
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=20240419200124.701cafb0@kernel.org \
--to=kuba@kernel.org \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=jun.gu@easystack.cn \
--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;
as well as URLs for NNTP newsgroup(s).