[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85a32259-d523-49ed-9441-634e4c2e881b@intel.com>
Date: Wed, 20 Nov 2024 15:40:36 +0100
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Toke Høiland-Jørgensen <toke@...hat.com>, "Alexei
Starovoitov" <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, "John
Fastabend" <john.fastabend@...il.com>, Andrii Nakryiko <andrii@...nel.org>,
Maciej Fijalkowski <maciej.fijalkowski@...el.com>, Stanislav Fomichev
<sdf@...ichev.me>, Magnus Karlsson <magnus.karlsson@...el.com>,
<nex.sw.ncis.osdt.itp.upstreaming@...el.com>, <bpf@...r.kernel.org>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next v5 00/19] xdp: a fistful of generic changes
(+libeth_xdp)
From: Jakub Kicinski <kuba@...nel.org>
Date: Tue, 19 Nov 2024 06:25:43 -0800
> On Tue, 19 Nov 2024 13:06:56 +0100 Alexander Lobakin wrote:
>>> This clearly could be multiple series, please don't go over the limit.
>>
>> Sorta.
>> I think I'll split it into two: changing the current logic + adding new
>> functions and libeth_xdp. Maybe I could merge the second one with the
>> Chapter IV, will see.
>
> FWIW I was tempted to cherry-pick patches 2, 4, 5, 6, and 7, since they
> look uncontroversial and stand on their own. But wasn't 100% sure I'm
> not missing a dependency. Then I thought - why take the risk, let me
> complain instead :) Easier to make progress with smaller series..
Sure, I understand. I wasn't sure it's not too much for one series, in
such cases, I let the reviewers choose :)
Thanks,
Olek
Powered by blists - more mailing lists