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, jacob.e.keller@intel.com,
jiri@resnulli.us, sdf@google.com, donald.hunter@redhat.com
Subject: Re: [PATCH net-next v3 0/6] tools/net/ynl: Add support for nlctrl netlink family
Date: Fri, 08 Mar 2024 05:00:37 +0000 [thread overview]
Message-ID: <170987403719.8362.3858488476279704879.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240306231046.97158-1-donald.hunter@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Mar 2024 23:10:40 +0000 you wrote:
> This series adds a new YNL spec for the nlctrl family, plus some fixes
> and enhancements for ynl.
>
> Patch 1 fixes an extack decoding bug
> Patch 2 gives cleaner netlink error reporting
> Patch 3 fixes an array-nest codegen bug
> Patch 4 adds nest-type-value support to ynl
> Patch 5 fixes the ynl schemas to allow empty enum-name attrs
> Patch 6 contains the nlctrl spec
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] tools/net/ynl: Fix extack decoding for netlink-raw
https://git.kernel.org/netdev/net-next/c/cecbc52c46e2
- [net-next,v3,2/6] tools/net/ynl: Report netlink errors without stacktrace
https://git.kernel.org/netdev/net-next/c/771b7012e5f3
- [net-next,v3,3/6] tools/net/ynl: Fix c codegen for array-nest
https://git.kernel.org/netdev/net-next/c/6fe7de5e9c08
- [net-next,v3,4/6] tools/net/ynl: Add nest-type-value decoding
https://git.kernel.org/netdev/net-next/c/b6e6a76dec33
- [net-next,v3,5/6] doc/netlink: Allow empty enum-name in ynl specs
https://git.kernel.org/netdev/net-next/c/bc52b39309c3
- [net-next,v3,6/6] doc/netlink/specs: Add spec for nlctrl netlink family
https://git.kernel.org/netdev/net-next/c/768e044a5fd4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-08 5:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:10 [PATCH net-next v3 0/6] tools/net/ynl: Add support for nlctrl netlink family Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 1/6] tools/net/ynl: Fix extack decoding for netlink-raw Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 2/6] tools/net/ynl: Report netlink errors without stacktrace Donald Hunter
2024-03-07 9:31 ` Breno Leitao
2024-03-07 11:56 ` Donald Hunter
2024-03-07 15:58 ` Jakub Kicinski
2024-03-08 18:27 ` Breno Leitao
2024-03-08 19:16 ` Jakub Kicinski
2024-03-06 23:10 ` [PATCH net-next v3 3/6] tools/net/ynl: Fix c codegen for array-nest Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 4/6] tools/net/ynl: Add nest-type-value decoding Donald Hunter
2024-03-06 23:10 ` [PATCH net-next v3 5/6] doc/netlink: Allow empty enum-name in ynl specs Donald Hunter
2024-03-07 2:26 ` Jakub Kicinski
2024-03-07 9:08 ` Donald Hunter
2024-03-07 15:21 ` Jakub Kicinski
2024-03-06 23:10 ` [PATCH net-next v3 6/6] doc/netlink/specs: Add spec for nlctrl netlink family Donald Hunter
2024-03-08 5:00 ` 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=170987403719.8362.3858488476279704879.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=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--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.