[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180417.113548.676760038759107548.davem@davemloft.net>
Date: Tue, 17 Apr 2018 11:35:48 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: daniel@...earbox.net
Cc: alexei.starovoitov@...il.com, brouer@...hat.com,
netdev@...r.kernel.org, bjorn.topel@...el.com,
magnus.karlsson@...el.com, eugenia@...lanox.com,
jasowang@...hat.com, john.fastabend@...il.com, eranbe@...lanox.com,
saeedm@...lanox.com, galp@...lanox.com, borkmann@...earbox.net,
tariqt@...lanox.com
Subject: Re: [net-next V11 PATCH 00/17] XDP redirect memory return API
From: Daniel Borkmann <daniel@...earbox.net>
Date: Tue, 17 Apr 2018 17:24:03 +0200
> On 04/17/2018 05:18 PM, David Miller wrote:
>> From: Alexei Starovoitov <alexei.starovoitov@...il.com>
>> Date: Tue, 17 Apr 2018 07:48:42 -0700
>>
>>> On Tue, Apr 17, 2018 at 04:45:16PM +0200, Jesper Dangaard Brouer wrote:
>>>> Submitted against net-next, as it contains NIC driver changes.
>>>>
>>>> This patchset works towards supporting different XDP RX-ring memory
>>>> allocators. As this will be needed by the AF_XDP zero-copy mode.
>> ...
>>> The series look good to me now.
>>> Acked-by: Alexei Starovoitov <ast@...nel.org>
>>
>> Pushed out to net-next, thanks everyone!
>
> See my comment on the last patch which is actually buggy. But given it's
> pushed out already, then it needs to be fixed as follow-up..
Yes it will need to be dealt with as a follow-up.
Powered by blists - more mailing lists