All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, donald.hunter@gmail.com, sdf@google.com
Subject: Re: [PATCH net-next 2/3] tools: ynl: generate code for ovs families
Date: Fri, 2 Feb 2024 11:24:15 +0100	[thread overview]
Message-ID: <ZbzCz4RuiZh-2Z4k@nanopsycho> (raw)
In-Reply-To: <20240202004926.447803-3-kuba@kernel.org>

Fri, Feb 02, 2024 at 01:49:25AM CET, kuba@kernel.org wrote:
>Add ovs_flow, ovs_vport and ovs_datapath to the families supported
>in C. ovs-flow has some circular nesting which is fun to deal with,
>but the necessary support has been added already in the previous
>release cycle.
>
>Add a sample that proves that dealing with fixed headers does
>actually work correctly.
>
>Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Reviewed-by: Jiri Pirko <jiri@nvidia.com>

  reply	other threads:[~2024-02-02 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  0:49 [PATCH net-next 0/3] tools: ynl: auto-gen for all genetlink families Jakub Kicinski
2024-02-02  0:49 ` [PATCH net-next 1/3] tools: ynl: include dpll and mptcp_pm in C codegen Jakub Kicinski
2024-02-02 10:21   ` Jiri Pirko
2024-02-02  0:49 ` [PATCH net-next 2/3] tools: ynl: generate code for ovs families Jakub Kicinski
2024-02-02 10:24   ` Jiri Pirko [this message]
2024-02-02  0:49 ` [PATCH net-next 3/3] tools: ynl: auto-gen for all genetlink families Jakub Kicinski
2024-02-02 10:25   ` Jiri Pirko
2024-02-03  5:20 ` [PATCH net-next 0/3] " 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=ZbzCz4RuiZh-2Z4k@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.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.