From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Babrou <ivan@cloudflare.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@cloudflare.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
willemdebruijn.kernel@gmail.com, dsahern@kernel.org,
peilin.ye@bytedance.com, rostedt@goodmis.org, petrm@nvidia.com,
nhorman@tuxdriver.com, satoru.moriya@hds.com
Subject: Re: [PATCH v2] udp6: add a missing call into udp_fail_queue_rcv_skb tracepoint
Date: Fri, 07 Jul 2023 08:20:20 +0000 [thread overview]
Message-ID: <168871802073.22009.17793808873391205698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230707043923.35578-1-ivan@cloudflare.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 6 Jul 2023 21:39:20 -0700 you wrote:
> The tracepoint has existed for 12 years, but it only covered udp
> over the legacy IPv4 protocol. Having it enabled for udp6 removes
> the unnecessary difference in error visibility.
>
> Signed-off-by: Ivan Babrou <ivan@cloudflare.com>
> Fixes: 296f7ea75b45 ("udp: add tracepoints for queueing skb to rcvbuf")
>
> [...]
Here is the summary with links:
- [v2] udp6: add a missing call into udp_fail_queue_rcv_skb tracepoint
https://git.kernel.org/netdev/net/c/8139dccd464a
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-07-07 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 4:39 [PATCH v2] udp6: add a missing call into udp_fail_queue_rcv_skb tracepoint Ivan Babrou
2023-07-07 6:40 ` Paolo Abeni
2023-07-07 8: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=168871802073.22009.17793808873391205698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=ivan@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=petrm@nvidia.com \
--cc=rostedt@goodmis.org \
--cc=satoru.moriya@hds.com \
--cc=willemdebruijn.kernel@gmail.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).