From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: davem@davemloft.net, daniel@iogearbox.net, peterz@infradead.org,
mhiramat@kernel.org, kuba@kernel.org, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: pull-request: bpf 2022-03-29
Date: Wed, 30 Mar 2022 04:10:12 +0000 [thread overview]
Message-ID: <164861341208.12150.15315859068081009865.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220329234924.39053-1-alexei.starovoitov@gmail.com>
Hello:
This pull request was applied to bpf/bpf.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Mar 2022 16:49:24 -0700 you wrote:
> Hi David, hi Jakub,
>
> The following pull-request contains BPF updates for your *net* tree.
>
> We've added 16 non-merge commits during the last 1 day(s) which contain
> a total of 24 files changed, 354 insertions(+), 187 deletions(-).
>
> [...]
Here is the summary with links:
- pull-request: bpf 2022-03-29
https://git.kernel.org/bpf/bpf/c/77c9387c0c5b
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:[~2022-03-30 4:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 23:49 pull-request: bpf 2022-03-29 Alexei Starovoitov
2022-03-30 1:41 ` Jakub Kicinski
2022-03-30 1:51 ` Alexei Starovoitov
2022-03-30 2:02 ` Jakub Kicinski
2022-03-30 4:52 ` Masami Hiramatsu
2022-03-30 9:15 ` Masami Hiramatsu
2022-03-30 15:09 ` Alexei Starovoitov
2022-03-31 1:11 ` [PATCH bpf] rethook: Fix to use WRITE_ONCE() for rethook::handler Masami Hiramatsu
2022-03-31 2:30 ` patchwork-bot+netdevbpf
2022-03-31 1:12 ` pull-request: bpf 2022-03-29 Masami Hiramatsu
2022-03-30 8:05 ` Jiri Olsa
2022-03-30 11:01 ` Jiri Olsa
2022-03-30 4:10 ` 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=164861341208.12150.15315859068081009865.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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).