From: Jakub Kicinski <kuba@kernel.org>
To: patchwork-bot+netdevbpf@kernel.org
Cc: Daniel Borkmann <daniel@iogearbox.net>,
davem@davemloft.net, pabeni@redhat.com, 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 2023-01-28
Date: Fri, 27 Jan 2023 23:55:35 -0800 [thread overview]
Message-ID: <20230127235535.684cae41@kernel.org> (raw)
In-Reply-To: <167489221874.30137.5005634055300425754.git-patchwork-notify@kernel.org>
On Sat, 28 Jan 2023 07:50:18 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Here is the summary with links:
> - pull-request: bpf-next 2023-01-28
> https://git.kernel.org/netdev/net/c/0548c5f26a0f
The bot's still matching on wrong PRs. I'll push this one shortly.
prev parent reply other threads:[~2023-01-28 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 0:48 pull-request: bpf-next 2023-01-28 Daniel Borkmann
2023-01-28 7:50 ` patchwork-bot+netdevbpf
2023-01-28 7:55 ` Jakub Kicinski [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=20230127235535.684cae41@kernel.org \
--to=kuba@kernel.org \
--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=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).