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: <3e9e10f34215b4d6b3a7361971df3c93d4b25419.camel@sipsolutions.net>
Date:   Mon, 14 Mar 2022 21:45:11 +0100
From:   Johannes Berg <johannes@...solutions.net>
To:     Jakub Kicinski <kuba@...nel.org>
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, 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.

> 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.

> > 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 :(

Right.

Anyway, was just thinking out loud I guess.

johannes