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, willemb@google.com
Subject: Re: [PATCH net 0/2] netlink: specs: rt-link: decode ip6gre
Date: Thu, 05 Jun 2025 11:00:32 +0000 [thread overview]
Message-ID: <174912123201.3027322.6365503905744814596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250603135357.502626-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 3 Jun 2025 06:53:55 -0700 you wrote:
> Adding GRE tunnels to the .config for driver tests caused
> some unhappiness in YNL, as it can't decode all the link
> attrs on the system. Add ip6gre support to fix the tests.
> This is similar to commit 6ffdbb93a59c ("netlink: specs:
> rt_link: decode ip6tnl, vti and vti6 link attrs").
>
> Jakub Kicinski (2):
> netlink: specs: rt-link: add missing byte-order properties
> netlink: specs: rt-link: decode ip6gre
>
> [...]
Here is the summary with links:
- [net,1/2] netlink: specs: rt-link: add missing byte-order properties
https://git.kernel.org/netdev/net/c/de92258e3b22
- [net,2/2] netlink: specs: rt-link: decode ip6gre
https://git.kernel.org/netdev/net/c/8af7a919c52f
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-06-05 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 13:53 [PATCH net 0/2] netlink: specs: rt-link: decode ip6gre Jakub Kicinski
2025-06-03 13:53 ` [PATCH net 1/2] netlink: specs: rt-link: add missing byte-order properties Jakub Kicinski
2025-06-04 8:56 ` Donald Hunter
2025-06-03 13:53 ` [PATCH net 2/2] netlink: specs: rt-link: decode ip6gre Jakub Kicinski
2025-06-04 8:58 ` Donald Hunter
2025-06-05 11: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=174912123201.3027322.6365503905744814596.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemb@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.