From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
pabeni@redhat.com, edumazet@google.com, ast@kernel.org,
andrii@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf-next 2022-04-27
Date: Wed, 27 Apr 2022 17:05:26 -0700 [thread overview]
Message-ID: <20220427170526.57d907d2@kernel.org> (raw)
In-Reply-To: <165110050658.2033.16722871450848438620.git-patchwork-notify@kernel.org>
On Wed, 27 Apr 2022 23:01:46 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Hello:
>
> This pull request was applied to bpf/bpf.git (master)
> by Jakub Kicinski <kuba@kernel.org>:
Boty McBotface still confusing bpf and bpf-next PRs :(
Pulling now.
No chance we can silence the "should be static" warnings?
The new unpriv_ebpf_notify() in particular seems like it could
use a header declaration - if someone is supposed to override it
they better match the prototype?
next prev parent reply other threads:[~2022-04-28 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 22:47 pull-request: bpf-next 2022-04-27 Daniel Borkmann
2022-04-27 23:01 ` patchwork-bot+netdevbpf
2022-04-28 0:05 ` Jakub Kicinski [this message]
2022-04-28 0:26 ` Andrii Nakryiko
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=20220427170526.57d907d2@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=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 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.