public inbox for netdev@vger.kernel.org 
 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/6] ynl: add support for user headers and struct attrs
Date: Thu, 23 Mar 2023 03:50:18 +0000	[thread overview]
Message-ID: <167954341843.25225.317267332666975407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230319193803.97453-1-donald.hunter@gmail.com>

Hello:

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

On Sun, 19 Mar 2023 19:37:57 +0000 you wrote:
> Add support for user headers and struct attrs to YNL. This patchset adds
> features to ynl and add a partial spec for openvswitch that demonstrates
> use of the features.
> 
> Patch 1 fixes a trivial signedness mismatch with struct genlmsghdr
> Patch 2-5 add features to ynl
> Patch 6 adds partial openvswitch specs that demonstrate the new features
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] tools: ynl: Fix genlmsg header encoding formats
    https://git.kernel.org/netdev/net/c/758d29fb3a8b
  - [net-next,v2,2/6] tools: ynl: Add struct parsing to nlspec
    (no matching commit)
  - [net-next,v2,3/6] tools: ynl: Add array-nest attr decoding to ynl
    (no matching commit)
  - [net-next,v2,4/6] tools: ynl: Add struct attr decoding to ynl
    (no matching commit)
  - [net-next,v2,5/6] tools: ynl: Add fixed-header support to ynl
    (no matching commit)
  - [net-next,v2,6/6] netlink: specs: add partial specification for openvswitch
    (no matching commit)

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-03-23  3:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 19:37 [PATCH net-next v2 0/6] ynl: add support for user headers and struct attrs Donald Hunter
2023-03-19 19:37 ` [PATCH net-next v2 1/6] tools: ynl: Fix genlmsg header encoding formats Donald Hunter
2023-03-19 19:37 ` [PATCH net-next v2 2/6] tools: ynl: Add struct parsing to nlspec Donald Hunter
2023-03-22  5:22   ` Jakub Kicinski
2023-03-22 11:38     ` Donald Hunter
2023-03-22 18:25       ` Jakub Kicinski
2023-03-19 19:38 ` [PATCH net-next v2 3/6] tools: ynl: Add array-nest attr decoding to ynl Donald Hunter
2023-03-22  5:18   ` Jakub Kicinski
2023-03-22 11:27     ` Donald Hunter
2023-03-22 18:27       ` Jakub Kicinski
2023-03-19 19:38 ` [PATCH net-next v2 4/6] tools: ynl: Add struct " Donald Hunter
2023-03-22  5:30   ` Jakub Kicinski
2023-03-22 11:48     ` Donald Hunter
2023-03-22 18:37       ` Jakub Kicinski
2023-03-22 22:06         ` Donald Hunter
2023-03-19 19:38 ` [PATCH net-next v2 5/6] tools: ynl: Add fixed-header support " Donald Hunter
2023-03-22  5:34   ` Jakub Kicinski
2023-03-22 11:54     ` Donald Hunter
2023-03-19 19:38 ` [PATCH net-next v2 6/6] netlink: specs: add partial specification for openvswitch Donald Hunter
2023-03-23  3:50 ` 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=167954341843.25225.317267332666975407.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=donald.hunter@gmail$(echo .)com \
    --cc=donald.hunter@redhat$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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