netdev - Re: pull-request: wireless-next-2022-03-11

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 14 Mar 2022 13:51:41 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Johannes Berg <johannes@...solutions.net>
Cc:     Kalle Valo <kvalo@...nel.org>, netdev@...r.kernel.org,
        linux-wireless@...r.kernel.org
Subject: Re: pull-request: wireless-next-2022-03-11

On Mon, 14 Mar 2022 21:45:11 +0100 Johannes Berg wrote:
> On Mon, 2022-03-14 at 13:41 -0700, Jakub Kicinski wrote:
> > 
> > Depends on what you mean. The bot currently understands the netdev +
> > bpf pw instance so it determines the target tree between those four.  
> 
> Makes sense, that's what it was written for :)
> 
> On the linux-wireless patchwork instance
> (https://patchwork.kernel.org/project/linux-wireless/) there are only
> two trees now, I think, wireless/main and wireless-next/main. Perhaps
> mt76 but maybe we'll just bring those into the fold too. Oh, I guess
> Kalle has some ath* trees too, not sure now.

Plus you need to know which series to ignore so that the occasional
cross-posted 50-patch series touching kernel.h doesn't take the build
bot out for 2 days :)

> > We'd need to teach it how to handle more trees, which would be a great
> > improvement, but requires coding.  
> 
> Right. Do you have it out in the open somewhere? Maybe we could even
> take it and run our own instance somewhere.

Oh yeah:

https://github.com/kuba-moo/nipa