[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4068b108-bd5a-4d09-97e9-4f9196b35eca@intel.com>
Date: Mon, 4 Nov 2024 15:36:34 +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 v3 10/18] xdp: get rid of xdp_frame::mem.id
From: Jakub Kicinski <kuba@...nel.org>
Date: Thu, 31 Oct 2024 17:41:07 -0700
> On Wed, 30 Oct 2024 17:51:53 +0100 Alexander Lobakin wrote:
>> - struct xdp_mem_info mem;
>> + enum xdp_mem_type mem_type:32;
>
> There is a new use of this field coming in from c40dd8c4732
> Can we wait for that to propagate to net-next ?
> I don't have any great ideas on how we can conditionally apply
> a fix up in the CI infra..
Good thing it happened already :D
Yeah I only need to assign mem_type instead of mem in that new place.
linux-next handles conflicts, but not our CI...
Thanks,
Olek
Powered by blists - more mailing lists