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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20220314134146.20fef5b9@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 14 Mar 2022 13:41:46 -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:17:30 +0100 Johannes Berg wrote:
> On Mon, 2022-03-14 at 11:37 -0700, Jakub Kicinski wrote:
> > Yeah.. patchwork build thing can't resolve conflicts. I wish there was
> > a way to attach a resolution to the PR so that the bot can use it :S
> 
> That'd be on thing - but OTOH ... maybe you/we could somehow attach the
> bot that processes things on the netdev patchwork also to the wireless
> one? It's on the same patchwork instance already, so ...

Depends on what you mean. The bot currently understands the netdev +
bpf pw instance so it determines the target tree between those four.

We'd need to teach it how to handle more trees, which would be a great
improvement, but requires coding.

> But I do't know who runs it, how it runs, who's paying for it, etc.

Yeah... As much as I'd love to give you root on the VM having it under
the corporate account is the only way I can get it paid for :(