From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, kuba@kernel.org, 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-03-06
Date: Tue, 07 Mar 2023 04:35:20 +0000 [thread overview]
Message-ID: <167816372051.12713.8574521202926153502.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230307004346.27578-1-daniel@iogearbox.net>
Hello:
This pull request was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Mar 2023 01:43:46 +0100 you wrote:
> Hi David, hi Jakub, hi Paolo, hi Eric,
>
> The following pull-request contains BPF updates for your *net-next* tree.
>
> There is a small conflict once net tree gets merged into net-next
> between commit b7abcd9c656b ("bpf, doc: Link to submitting-patches.rst
> for general patch submission info") from the bpf tree and commit
> d56b0c461d19 ("bpf, docs: Fix link to netdev-FAQ target") from the
> bpf-next tree. Follow Stephen's resolution:
> https://lore.kernel.org/bpf/20230307095812.236eb1be@canb.auug.org.au/
>
> [...]
Here is the summary with links:
- pull-request: bpf-next 2023-03-06
https://git.kernel.org/netdev/net/c/757b56a6c7bb
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-03-07 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 0:43 pull-request: bpf-next 2023-03-06 Daniel Borkmann
2023-03-07 4:35 ` patchwork-bot+netdevbpf [this message]
2023-03-07 4:47 ` Jakub Kicinski
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=167816372051.12713.8574521202926153502.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).