From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, sdf@fomichev.me, gal@nvidia.com,
jstancek@redhat.com, ast@fiberby.net
Subject: Re: [PATCH net-next v2 0/2] tools: ynl: pyynl: pull the --family resolution logic into the lib
Date: Fri, 03 Jul 2026 07:00:14 +0000 [thread overview]
Message-ID: <178306201441.2494164.5489624175962014946.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701021751.3234681-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 30 Jun 2026 19:17:49 -0700 you wrote:
> When packaging YNL as a system level utility we added a --family
> argument which auto-resolves the full spec path from a well known
> path in /usr/share. Spelling out full YAML spec files is at this
> point only done in-tree, for example in the selftests which need
> the very latest YAML. But the selftests have their own wrapping
> classes for each family so test authors aren't really bothered
> by having to spell the paths out.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] tools: ynl: pyynl: re-export the library API from the package root
https://git.kernel.org/netdev/net-next/c/df87e5c4e94e
- [net-next,v2,2/2] tools: ynl: pyynl: pull the --family resolution logic into the lib
https://git.kernel.org/netdev/net-next/c/10c90f1bba3a
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:[~2026-07-03 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 2:17 [PATCH net-next v2 0/2] tools: ynl: pyynl: pull the --family resolution logic into the lib Jakub Kicinski
2026-07-01 2:17 ` [PATCH net-next v2 1/2] tools: ynl: pyynl: re-export the library API from the package root Jakub Kicinski
2026-07-01 2:17 ` [PATCH net-next v2 2/2] tools: ynl: pyynl: pull the --family resolution logic into the lib Jakub Kicinski
2026-07-01 9:46 ` Donald Hunter
2026-07-03 7: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=178306201441.2494164.5489624175962014946.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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.