Development discussion of WireGuard
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: Jason@zx2c4.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
	horms@kernel.org, jacob.e.keller@intel.com, sd@queasysnail.net,
	wireguard@lists.zx2c4.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 00/11] tools: ynl: prepare for wireguard
Date: Tue, 16 Sep 2025 15:38:03 +0000	[thread overview]
Message-ID: <175803708374.1166060.16728108514341236086.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250915144301.725949-1-ast@fiberby.net>

Hello:

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

On Mon, 15 Sep 2025 14:42:45 +0000 you wrote:
> This series contains the last batch of YNL changes to support
> the wireguard YNL conversion.
> 
> The wireguard changes, to be applied on top of this series,
> has been posted as an RFC series here:
>   https://lore.kernel.org/netdev/20250904-wg-ynl-rfc@fiberby.net/
> 
> [...]

Here is the summary with links:
  - [net-next,v5,01/11] tools: ynl-gen: allow overriding name-prefix for constants
    https://git.kernel.org/netdev/net-next/c/3ff5258b9781
  - [net-next,v5,02/11] tools: ynl-gen: generate nested array policies
    https://git.kernel.org/netdev/net-next/c/d0bdfe36d777
  - [net-next,v5,03/11] tools: ynl-gen: add sub-type check
    https://git.kernel.org/netdev/net-next/c/8df78d97e498
  - [net-next,v5,04/11] tools: ynl-gen: refactor local vars for .attr_put() callers
    https://git.kernel.org/netdev/net-next/c/db4ea3baa484
  - [net-next,v5,05/11] tools: ynl-gen: avoid repetitive variables definitions
    https://git.kernel.org/netdev/net-next/c/099902fc66f8
  - [net-next,v5,06/11] tools: ynl-gen: validate nested arrays
    https://git.kernel.org/netdev/net-next/c/1d99aa4ed707
  - [net-next,v5,07/11] tools: ynl-gen: rename TypeArrayNest to TypeIndexedArray
    https://git.kernel.org/netdev/net-next/c/a44a93ea6f06
  - [net-next,v5,08/11] tools: ynl: move nest packing to a helper function
    https://git.kernel.org/netdev/net-next/c/328c13426240
  - [net-next,v5,09/11] tools: ynl: encode indexed-arrays
    https://git.kernel.org/netdev/net-next/c/5c51ae2446c2
  - [net-next,v5,10/11] tools: ynl: decode hex input
    https://git.kernel.org/netdev/net-next/c/52550d518d24
  - [net-next,v5,11/11] tools: ynl: add ipv4-or-v6 display hint
    https://git.kernel.org/netdev/net-next/c/1b255e1beabf

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



  parent reply	other threads:[~2025-09-16 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250915144301.725949-1-ast@fiberby.net>
     [not found] ` <20250915144301.725949-5-ast@fiberby.net>
2025-09-16  1:42   ` [PATCH net-next v5 04/11] tools: ynl-gen: refactor local vars for .attr_put() callers Jakub Kicinski
     [not found] ` <20250915144301.725949-6-ast@fiberby.net>
2025-09-16  1:42   ` [PATCH net-next v5 05/11] tools: ynl-gen: avoid repetitive variables definitions Jakub Kicinski
     [not found] ` <20250915144301.725949-7-ast@fiberby.net>
2025-09-16  1:42   ` [PATCH net-next v5 06/11] tools: ynl-gen: validate nested arrays Jakub Kicinski
     [not found] ` <20250915144301.725949-8-ast@fiberby.net>
2025-09-16  1:43   ` [PATCH net-next v5 07/11] tools: ynl-gen: rename TypeArrayNest to TypeIndexedArray Jakub Kicinski
2025-09-16 15:38 ` patchwork-bot+netdevbpf [this message]
2025-09-16 15:53 ` [PATCH net-next v5 00/11] tools: ynl: prepare for wireguard Jason A. Donenfeld
2025-09-16 22:39   ` Jakub Kicinski

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=175803708374.1166060.16728108514341236086.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=Jason@zx2c4.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=wireguard@lists.zx2c4.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).