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/2] tcp_metrics: add netlink protocol spec in YAML
Date: Mon, 01 Jul 2024 08:50:30 +0000 [thread overview]
Message-ID: <171982383050.18736.4428619199553157199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240627213551.3147327-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 27 Jun 2024 14:35:49 -0700 you wrote:
> Add a netlink protocol spec for the tcp_metrics generic netlink family.
> First patch adjusts the uAPI header guards to make it easier to build
> tools/ with non-system headers.
>
> v1: https://lore.kernel.org/all/20240626201133.2572487-1-kuba@kernel.org
>
> Jakub Kicinski (2):
> tcp_metrics: add UAPI to the header guard
> tcp_metrics: add netlink protocol spec in YAML
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] tcp_metrics: add UAPI to the header guard
https://git.kernel.org/netdev/net-next/c/7c8110057b1b
- [net-next,v2,2/2] tcp_metrics: add netlink protocol spec in YAML
https://git.kernel.org/netdev/net-next/c/85674625e0bc
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-07-01 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 21:35 [PATCH net-next v2 0/2] tcp_metrics: add netlink protocol spec in YAML Jakub Kicinski
2024-06-27 21:35 ` [PATCH net-next v2 1/2] tcp_metrics: add UAPI to the header guard Jakub Kicinski
2024-06-28 10:23 ` Donald Hunter
2024-06-27 21:35 ` [PATCH net-next v2 2/2] tcp_metrics: add netlink protocol spec in YAML Jakub Kicinski
2024-06-28 10:24 ` Donald Hunter
2024-07-01 8: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=171982383050.18736.4428619199553157199.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).