[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de14fefc-a8c1-ff6c-5354-8cce4a3f66f9@redhat.com>
Date: Mon, 29 Nov 2021 15:29:07 +0100
From: Jesper Dangaard Brouer <jbrouer@...hat.com>
To: Alexander Lobakin <alexandr.lobakin@...el.com>
Cc: brouer@...hat.com, netdev@...r.kernel.org, bpf@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Daniel Borkmann <borkmann@...earbox.net>,
jesse.brandeburg@...el.com, intel-wired-lan@...ts.osuosl.org,
magnus.karlsson@...el.com, bjorn@...nel.org,
Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>
Subject: Re: [PATCH net-next 0/2] igc: driver change to support XDP metadata
On 29/11/2021 15.10, Alexander Lobakin wrote:
> From: Jesper Dangaard Brouer <brouer@...hat.com>
> Date: Mon, 15 Nov 2021 21:36:20 +0100
>
>> Changes to fix and enable XDP metadata to a specific Intel driver igc.
>> Tested with hardware i225 that uses driver igc, while testing AF_XDP
>> access to metadata area.
>
> Would you mind if I take this your series into my bigger one that
> takes care of it throughout all the Intel drivers?
I have a customer that depend on this fix. They will have to do the
backport anyway (to v5.13), but it would bring confidence on their side
if the commits appear in an official git-tree before doing the backport
(and optimally with a SHA they can refer to).
Tony Nguyen have these landed in your git-tree?
--JEsper
Powered by blists - more mailing lists