netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Donald Hunter <donald.hunter@gmail.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, donald.hunter@redhat.com
Subject: Re: [PATCH net-next v2 0/4] netlink: specs: add ynl spec for ovs_flow
Date: Tue, 30 May 2023 05:10:20 +0000	[thread overview]
Message-ID: <168542342083.26777.11973834461536613804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230527133107.68161-1-donald.hunter@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 27 May 2023 14:31:03 +0100 you wrote:
> Add a ynl specification for ovs_flow. The spec is sufficient to dump ovs
> flows but some attrs have been left as binary blobs because ynl doesn't
> support C arrays in struct definitions yet.
> 
> Patches 1-3 add features for genetlink-legacy specs
> Patch 4 is the ovs_flow netlink spec
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/4] doc: ynl: Add doc attr to struct members in genetlink-legacy spec
    https://git.kernel.org/netdev/net-next/c/6d6bae63053d
  - [net-next,v2,2/4] tools: ynl: Initialise fixed headers to 0 in genetlink-legacy
    https://git.kernel.org/netdev/net-next/c/5ac18889bde0
  - [net-next,v2,3/4] tools: ynl: Support enums in struct members in genetlink-legacy
    https://git.kernel.org/netdev/net-next/c/313a7a808ca8
  - [net-next,v2,4/4] netlink: specs: add ynl spec for ovs_flow
    https://git.kernel.org/netdev/net-next/c/93b230b549bc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-30  5:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 13:31 [PATCH net-next v2 0/4] netlink: specs: add ynl spec for ovs_flow Donald Hunter
2023-05-27 13:31 ` [PATCH net-next v2 1/4] doc: ynl: Add doc attr to struct members in genetlink-legacy spec Donald Hunter
2023-05-27 13:31 ` [PATCH net-next v2 2/4] tools: ynl: Initialise fixed headers to 0 in genetlink-legacy Donald Hunter
2023-05-27 13:31 ` [PATCH net-next v2 3/4] tools: ynl: Support enums in struct members " Donald Hunter
2023-05-27 13:31 ` [PATCH net-next v2 4/4] netlink: specs: add ynl spec for ovs_flow Donald Hunter
2023-05-30  5:10 ` patchwork-bot+netdevbpf [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=168542342083.26777.11973834461536613804.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=donald.hunter@redhat.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.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 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).