netdev - Re: [net-next V9 PATCH 00/16] XDP redirect memory return API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 03 Apr 2018 12:23:38 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     brouer@...hat.com
Cc:     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,
        alexei.starovoitov@...il.com, tariqt@...lanox.com
Subject: Re: [net-next V9 PATCH 00/16] XDP redirect memory return API

From: Jesper Dangaard Brouer <brouer@...hat.com>
Date: Tue, 3 Apr 2018 18:07:16 +0200

> On Tue, 03 Apr 2018 10:54:27 -0400 (EDT)
> David Miller <davem@...emloft.net> wrote:
> 
>> Don't worry, just resubmit when net-next opens back up.
> 
> At that point in time, should I got back to posting it against the
> bpf-next git-tree again? Any preferences from Mellanox or BPF-guys?

I have no personal preference, although it's probably best to go
through the bpf-next tree.

> ... It have been a bit of a pain to keep track of driver changes in
> net-next, and waiting for them to get merged into bpf-next.

I totally understand :)