From: Paolo Abeni <pabeni@redhat.com>
To: patchwork-bot+netdevbpf@kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf-next 2024-07-08
Date: Tue, 09 Jul 2024 17:00:31 +0200 [thread overview]
Message-ID: <25cdf00fe435dfe4f2e18aeb645245cd8fb99f20.camel@redhat.com> (raw)
In-Reply-To: <172053542890.29513.3572609329958435109.git-patchwork-notify@kernel.org>
On Tue, 2024-07-09 at 14:30 +0000, patchwork-bot+netdevbpf@kernel.org
wrote:
> This pull request was applied to netdev/net.git (main)
> by Paolo Abeni <pabeni@redhat.com>:
FTR, I did not. The bot just went wild.
/P
prev parent reply other threads:[~2024-07-09 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 22:14 pull-request: bpf-next 2024-07-08 Daniel Borkmann
2024-07-09 14:30 ` patchwork-bot+netdevbpf
2024-07-09 15:00 ` Paolo Abeni [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=25cdf00fe435dfe4f2e18aeb645245cd8fb99f20.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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).