netdev - Re: [PATCHv17 bpf-next 0/6] xdp: add a new helper for dev map multicast support

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]

Message-ID: <20210204031236.GC2900@Leo-laptop-t470s>
Date:   Thu, 4 Feb 2021 11:12:36 +0800
From:   Hangbin Liu <liuhangbin@...il.com>
To:     John Fastabend <john.fastabend@...il.com>
Cc:     Daniel Borkmann <daniel@...earbox.net>,
        Alexei Starovoitov <alexei.starovoitov@...il.com>,
        netdev@...r.kernel.org,
        Toke Høiland-Jørgensen <toke@...hat.com>,
        Jiri Benc <jbenc@...hat.com>,
        Jesper Dangaard Brouer <brouer@...hat.com>,
        Eelco Chaudron <echaudro@...hat.com>, ast@...nel.org,
        bpf@...r.kernel.org,
        Lorenzo Bianconi <lorenzo.bianconi@...hat.com>,
        David Ahern <dsahern@...il.com>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>,
        Maciej Fijalkowski <maciej.fijalkowski@...el.com>
Subject: Re: [PATCHv17 bpf-next 0/6] xdp: add a new helper for dev map
 multicast support

On Wed, Feb 03, 2021 at 06:53:20PM -0800, John Fastabend wrote:
> Hangbin Liu wrote:
> > Hi Daniel, Alexei,
> > 
> > It has been one week after Maciej, Toke, John's review/ack. What should
> > I do to make a progress for this patch set?
> > 
> 
> Patchwork is usually the first place to check:

Thanks John for the link.
> 
>  https://patchwork.kernel.org/project/netdevbpf/list/?series=421095&state=*

Before I sent the email I only checked link
https://patchwork.kernel.org/project/netdevbpf/list/ but can't find my patch.

How do you get the series number?

> 
> Looks like it was marked changed requested. After this its unlikely
> anyone will follow up on it, rightly so given the assumption another
> revision is coming.
> 
> In this case my guess is it was moved into changes requested because
> I asked for a change, but then after some discussion you convinced me
> the change was not in fact needed.
> 
> Alexei, Daniel can probably tell you if its easier to just send a v18
> or pull in the v17 assuming any final reviews don't kick anything
> else up.

OK, I will wait for Alexei, Daniel and see if I need to do a rebase.

Thanks
Hangbin