From: Jakub Kicinski <kuba@kernel.org>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
donald.hunter@redhat.com
Subject: Re: [PATCH net-next v1] netlink: specs: fixup openvswitch specs for code generation
Date: Thu, 15 Jun 2023 20:03:39 -0700 [thread overview]
Message-ID: <20230615200339.3601385d@kernel.org> (raw)
In-Reply-To: <20230615151405.77649-1-donald.hunter@gmail.com>
On Thu, 15 Jun 2023 16:14:05 +0100 Donald Hunter wrote:
> Refine the ovs_* specs to align exactly with the ovs netlink UAPI
> definitions to enable code generation.
Hah, the C code gen really tells you if you got the spec right ;)
Changes LGTM!
next prev parent reply other threads:[~2023-06-16 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 15:14 [PATCH net-next v1] netlink: specs: fixup openvswitch specs for code generation Donald Hunter
2023-06-16 3:03 ` Jakub Kicinski [this message]
2023-06-17 7:30 ` 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=20230615200339.3601385d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=donald.hunter@redhat.com \
--cc=edumazet@google.com \
--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 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).