From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, daniel@iogearbox.net, andrii@kernel.org,
torvalds@linuxfoundation.org, peterz@infradead.org,
brauner@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@fb.com
Subject: Re: pull-request: bpf-next 2023-12-18
Date: Tue, 19 Dec 2023 01:10:57 +0000 [thread overview]
Message-ID: <170294825725.17422.14867129364522571389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231219000520.34178-1-alexei.starovoitov@gmail.com>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 18 Dec 2023 16:05:20 -0800 you wrote:
> Hi David, hi Jakub, hi Paolo, hi Eric,
>
> The following pull-request contains BPF updates for your *net-next* tree.
>
> This PR is larger than usual and contains changes in various parts of the kernel.
>
> The main changes are:
>
> [...]
Here is the summary with links:
- pull-request: bpf-next 2023-12-18
https://git.kernel.org/netdev/net-next/c/c49b292d031e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-19 1:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 0:05 pull-request: bpf-next 2023-12-18 Alexei Starovoitov
2023-12-19 0:19 ` Alexei Starovoitov
2023-12-19 0:55 ` Jakub Kicinski
2023-12-19 1:17 ` Linus Torvalds
2023-12-19 1:10 ` patchwork-bot+netdevbpf [this message]
2023-12-19 1:11 ` Linus Torvalds
2023-12-19 1:48 ` Alexei Starovoitov
2023-12-19 3:57 ` Linus Torvalds
2023-12-19 4:34 ` Andrii Nakryiko
2023-12-19 5:38 ` Andrii Nakryiko
2023-12-19 10:23 ` Christian Brauner
2023-12-19 16:06 ` Matthew Wilcox
2023-12-19 16:51 ` Alexei Starovoitov
2023-12-19 16:36 ` Daniel Borkmann
2023-12-19 16:42 ` Alexei Starovoitov
2023-12-19 18:31 ` Andrii Nakryiko
2023-12-20 11:18 ` Christian Brauner
2023-12-20 19:17 ` Andrii Nakryiko
2023-12-21 13:05 ` Christian Brauner
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=170294825725.17422.14867129364522571389.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=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.