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, horms@kernel.org,
jstancek@redhat.com, jiri@resnulli.us, donald.hunter@redhat.com
Subject: Re: [PATCH net-next v2 1/2] tools/net/ynl: add support for --family and --list-families
Date: Tue, 14 Jan 2025 03:30:48 +0000 [thread overview]
Message-ID: <173682544851.3721274.8403975394235475360.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250111154803.7496-1-donald.hunter@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 11 Jan 2025 15:48:02 +0000 you wrote:
> Add a --family option to ynl to specify the spec by family name instead
> of file path, with support for searching in-tree and system install
> location and a --list-families option to show the available families.
>
> ./tools/net/ynl/pyynl/cli.py --family rt_addr --dump getaddr
>
> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] tools/net/ynl: add support for --family and --list-families
https://git.kernel.org/netdev/net-next/c/2ff80cefb77b
- [net-next,v2,2/2] tools/net/ynl: ethtool: support spec load from install location
https://git.kernel.org/netdev/net-next/c/b1b62d6d332e
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:[~2025-01-14 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 15:48 [PATCH net-next v2 1/2] tools/net/ynl: add support for --family and --list-families Donald Hunter
2025-01-11 15:48 ` [PATCH net-next v2 2/2] tools/net/ynl: ethtool: support spec load from install location Donald Hunter
2025-01-14 3:30 ` 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=173682544851.3721274.8403975394235475360.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=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=jstancek@redhat.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 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.