[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEf4BzaO5X2ubv1NX=qgCFQiXJXHriV=Ue=LkJt3ioiZYJJp1Q@mail.gmail.com>
Date: Wed, 27 Apr 2022 17:26:55 -0700
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Daniel Borkmann <daniel@...earbox.net>,
patchwork-bot+netdevbpf@...nel.org,
"David S. Miller" <davem@...emloft.net>, pabeni@...hat.com,
Eric Dumazet <edumazet@...gle.com>,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>,
Networking <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>
Subject: Re: pull-request: bpf-next 2022-04-27
On Wed, Apr 27, 2022 at 5:05 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> 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?
Seems like it will go through tip? ([0])
[0] https://lore.kernel.org/bpf/CAADnVQKjfQMG_zFf9F9P7m0UzqESs7XoRy=udqrDSodxa8yBpg@mail.gmail.com/
Powered by blists - more mailing lists