netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "jun.gu" <jun.gu@easystack.cn>
Cc: echaudro@redhat.com, dev@openvswitch.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4] net: openvswitch: Check vport netdev name
Date: Thu, 18 Apr 2024 08:38:45 -0700	[thread overview]
Message-ID: <20240418083845.3b1f2407@kernel.org> (raw)
In-Reply-To: <20240418023242.259542-1-jun.gu@easystack.cn>

On Thu, 18 Apr 2024 10:32:42 +0800 jun.gu wrote:
> +	if ((!vport->dev) || strcmp(name, ovs_vport_name(vport))) {

Please drop the unnecessary brackets.
When you repost, start a new thread, do not post new version
in-reply-to.
-- 
pw-bot: cr

  reply	other threads:[~2024-04-18 15:38 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 [this message]
     [not found]                 ` <20240419043133.117295-1-jun.gu@easystack.cn>
2024-04-20  3:01                   ` Jakub Kicinski
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=20240418083845.3b1f2407@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).