From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
jiri@resnulli.us, jacob.e.keller@intel.com, sdf@google.com
Subject: Re: [PATCHv3 net-next 0/2] doc/netlink/specs: Add vlan support
Date: Fri, 29 Mar 2024 01:11:50 +0000 [thread overview]
Message-ID: <171167471051.20385.16149210851709967859.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327123130.1322921-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Mar 2024 20:31:27 +0800 you wrote:
> Add vlan support in rt_link spec.
>
> Hangbin Liu (2):
> ynl: support hex display_hint for integer
> doc/netlink/specs: Add vlan attr in rt_link spec
>
> Documentation/netlink/specs/rt_link.yaml | 80 +++++++++++++++++++++++-
> tools/net/ynl/lib/ynl.py | 5 +-
> 2 files changed, 82 insertions(+), 3 deletions(-)
Here is the summary with links:
- [PATCHv3,net-next,1/2] ynl: support hex display_hint for integer
https://git.kernel.org/netdev/net-next/c/b334f5ed3d91
- [PATCHv3,net-next,2/2] doc/netlink/specs: Add vlan attr in rt_link spec
https://git.kernel.org/netdev/net-next/c/782c1084b9fa
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-29 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 12:31 [PATCHv3 net-next 0/2] doc/netlink/specs: Add vlan support Hangbin Liu
2024-03-27 12:31 ` [PATCHv3 net-next 1/2] ynl: support hex display_hint for integer Hangbin Liu
2024-03-27 12:31 ` [PATCHv3 net-next 2/2] doc/netlink/specs: Add vlan attr in rt_link spec Hangbin Liu
2024-03-28 15:05 ` Donald Hunter
2024-03-29 1:11 ` 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=171167471051.20385.16149210851709967859.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--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.