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, donald.hunter@gmail.com
Subject: Re: [PATCH net-next v2 0/3] netlink: specs: prep legacy specs for C code gen
Date: Fri, 15 Dec 2023 12:20:26 +0000 [thread overview]
Message-ID: <170264282616.26998.14952146049410897563.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231215015735.3419974-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 14 Dec 2023 17:57:32 -0800 you wrote:
> Minor adjustments to some specs to make them ready for C code gen.
>
> v2:
> - fix MAINATINERS and subject of patch 3
>
> Jakub Kicinski (3):
> netlink: specs: ovs: remove fixed header fields from attrs
> netlink: specs: ovs: correct enum names in specs
> netlink: specs: mptcp: rename the MPTCP path management spec
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] netlink: specs: ovs: remove fixed header fields from attrs
https://git.kernel.org/netdev/net-next/c/3ada0b33c454
- [net-next,v2,2/3] netlink: specs: ovs: correct enum names in specs
https://git.kernel.org/netdev/net-next/c/209bcb9af8f1
- [net-next,v2,3/3] netlink: specs: mptcp: rename the MPTCP path management spec
https://git.kernel.org/netdev/net-next/c/b059aef76c51
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:[~2023-12-15 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 1:57 [PATCH net-next v2 0/3] netlink: specs: prep legacy specs for C code gen Jakub Kicinski
2023-12-15 1:57 ` [PATCH net-next v2 1/3] netlink: specs: ovs: remove fixed header fields from attrs Jakub Kicinski
2023-12-15 1:57 ` [PATCH net-next v2 2/3] netlink: specs: ovs: correct enum names in specs Jakub Kicinski
2023-12-15 1:57 ` [PATCH net-next v2 3/3] netlink: specs: mptcp: rename the MPTCP path management spec Jakub Kicinski
2023-12-15 12:20 ` 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=170264282616.26998.14952146049410897563.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=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 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).