[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220427170526.57d907d2@kernel.org>
Date: Wed, 27 Apr 2022 17:05:26 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: patchwork-bot+netdevbpf@...nel.org, davem@...emloft.net,
pabeni@...hat.com, edumazet@...gle.com, ast@...nel.org,
andrii@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf-next 2022-04-27
On Wed, 27 Apr 2022 23:01:46 +0000 patchwork-bot+netdevbpf@...nel.org
wrote:
> Hello:
>
> This pull request was applied to bpf/bpf.git (master)
> by Jakub Kicinski <kuba@...nel.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?
Powered by blists - more mailing lists