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,
donald.hunter@redhat.com, idosch@nvidia.com, sdf@fomichev.me
Subject: Re: [PATCH net-next v3 0/2] netlink: specs: Add neigh and rule YNL specs
Date: Fri, 08 Nov 2024 04:50:37 +0000 [thread overview]
Message-ID: <173104143799.2196790.1518650944719093198.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241106090718.64713-1-donald.hunter@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Nov 2024 09:07:16 +0000 you wrote:
> Add YNL specs for the FDB neighbour tables and FIB rules from the
> rtnelink families.
>
> v2 -> v3:
> - removed spurious dump parameter, thanks to Ido Schimmel
>
> v1 -> v2:
> - added 'dscp' attribute, thanks to Ido Schimmel
> - fixed types in fib-rule-uid-range, thanks to Stanislav Fomichev
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] netlink: specs: Add a spec for neighbor tables in rtnetlink
https://git.kernel.org/netdev/net-next/c/bc515ed06652
- [net-next,v3,2/2] netlink: specs: Add a spec for FIB rule management
https://git.kernel.org/netdev/net-next/c/a852e3c35641
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-11-08 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:07 [PATCH net-next v3 0/2] netlink: specs: Add neigh and rule YNL specs Donald Hunter
2024-11-06 9:07 ` [PATCH net-next v3 1/2] netlink: specs: Add a spec for neighbor tables in rtnetlink Donald Hunter
2024-11-06 9:07 ` [PATCH net-next v3 2/2] netlink: specs: Add a spec for FIB rule management Donald Hunter
2024-11-07 1:25 ` [PATCH net-next v3 0/2] netlink: specs: Add neigh and rule YNL specs Jakub Kicinski
2024-11-08 4:50 ` 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=173104143799.2196790.1518650944719093198.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=idosch@nvidia.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 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).