From: Jakub Kicinski <kuba@kernel.org>
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
Ilya Maximets <i.maximets@ovn.org>
Subject: Re: [PATCH net-next v8 3/3] netlink: specs: correct the ovs specs where they do not match the kernel
Date: Wed, 18 Nov 2026 16:26:46 -0800 [thread overview]
Message-ID: <20261118162646.688c68c2@kernel.org> (raw)
In-Reply-To: <20261115072638.3163018-4-houminxi@gmail.com>
On Sun, 15 Nov 2026 02:26:38 -0500 Minxi Hou wrote:
> - * For other requests, if %OVS_VPORT_ATTR_NAME is specified then it is used to
> - * look up the vport to operate on; otherwise dp_idx from the &struct
> - * ovs_header plus %OVS_VPORT_ATTR_PORT_NO determine the vport.
> + * For requests other than new and dump, if %OVS_VPORT_ATTR_NAME is specified
> + * then it is used to look up the vport to operate on; otherwise dp_ifindex from
> */
AI points out this comment got cut off mid sentence
--
pw-bot: cr
prev parent reply other threads:[~2026-11-19 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 7:26 [PATCH net-next v8 0/3] netlink: specs: fill in the missing ovs operations Minxi Hou
2026-11-15 7:26 ` [PATCH net-next v8 1/3] netlink: specs: add ovs_flow del and set operations Minxi Hou
2026-11-15 7:26 ` [PATCH net-next v8 2/3] netlink: specs: add ovs datapath and vport " Minxi Hou
2026-11-15 7:26 ` [PATCH net-next v8 3/3] netlink: specs: correct the ovs specs where they do not match the kernel Minxi Hou
2026-11-19 0:26 ` Jakub Kicinski [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=20261118162646.688c68c2@kernel.org \
--to=kuba@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=echaudro@redhat.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=houminxi@gmail.com \
--cc=i.maximets@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.