[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM0EoMkJcVFx+u93T=PO_Q6BJuHe3h_GGW1=5h=asYFo--x=TQ@mail.gmail.com>
Date: Tue, 17 Oct 2023 11:38:39 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, anjali.singhai@...el.com,
namrata.limaye@...el.com, deb.chatterjee@...el.com,
john.andy.fingerhut@...el.com, dan.daly@...el.com, Vipin.Jain@....com,
tom@...anda.io, mleitner@...hat.com, Mahesh.Shirshyad@....com,
tomasz.osinski@...el.com, jiri@...nulli.us, xiyou.wangcong@...il.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
vladbu@...dia.com, horms@...nel.org, khalidm@...dia.com, toke@...hat.com,
mattyk@...dia.com
Subject: Re: [PATCH v7 net-next 00/18] Introducing P4TC
On Tue, Oct 17, 2023 at 11:00 AM Daniel Borkmann <daniel@...earbox.net> wrote:
>
> On 10/16/23 10:38 PM, Jamal Hadi Salim wrote:
> > On Mon, Oct 16, 2023 at 4:15 PM Jakub Kicinski <kuba@...nel.org> wrote:
> [...]
> >> FWIW please do not post another version this week (not that I think
> >> that you would do that, but better safe than sorry. Last week the patch
> >> bombs pushed the shared infra 24h+ behind the list..)
> >
> > Not intending to.
>
> Given bpf & kfuncs, please also Cc bpf@...r.kernel.org on future revisions
> as not everyone on bpf list is subscribed to netdev.
I thought i did that, maybe it was in earlier patches. Do you want Cc
on everything or only on kfuncs? I am getting conflicting messages, do
you have to Cc bpf for kfuncs?
Example, attached from (some fs?) conference last month i think
cheers,
jamal
Download attachment "kfunc-requirements.jpg" of type "image/jpeg" (121194 bytes)
Powered by blists - more mailing lists