linux-kernel - Re: Closing down the wireless trees for a summer break?

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:   Wed, 14 Jun 2023 11:56:16 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Toke Høiland-Jørgensen <toke@...nel.org>,
        Kalle Valo <kvalo@...nel.org>, linux-wireless@...r.kernel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev
Subject: Re: Closing down the wireless trees for a summer break?

On Tue, 2023-06-13 at 19:51 -0700, Jakub Kicinski wrote:
> On Tue, 13 Jun 2023 22:00:35 +0200 Johannes Berg wrote:
> > On Tue, 2023-06-13 at 11:28 -0700, Jakub Kicinski wrote:
> > > On Tue, 13 Jun 2023 20:14:40 +0200 Toke Høiland-Jørgensen wrote:  
> > > > I think this sounds reasonable, and I applaud the effort to take some
> > > > time off during the summer :)
> > > > 
> > > > One question that comes to mind is how would this work for patchwork?
> > > > Would we keep using the wireless patchwork instance for the patches
> > > > going to -net in that period, or will there be some other process for
> > > > this? I realise the setup we have for ath9k is a bit special in this
> > > > regard with the ack-on-list+delegation, so I'm obviously mostly
> > > > interested in what to do about that... :)  
> > > 
> > > Whatever's easiest :) It's probably a good idea for Kalle to write
> > > down all the local rules and customs and share those with us.
> > 
> > While that's probably a good idea regardless, I'd think that patchwork
> > doesn't really matter that much - we'll have some catching up to do
> > anyway after the vacations, so looking through patchwork etc. would be
> > perfectly acceptable. Worst case we'd notice when a patch doesn't apply,
> > right? :)
> 
> Right, I meant it more in terms of patch flow. Is looking at which
> drivers have a tree specified in MAINTAINERS enough to know what
> should be applied directly?

Oh, right. Not really sure how well that all is reflected in
MAINTAINERS.

So Gregory usually handles patches for iwlwifi, but he'll _also_ be on
vacation around a similar time frame.

Toke usually reviews patches for ath9k but then asks Kalle (via
assigning in patchwork) to apply them.

Felix usually picks up patches for mediatek drivers (unless specifically
asking Kalle for individual ones) and then sends a pull request.

For the stack (all the bits we have under net/) that's just on me,
normally.

I think that's it? But I guess Kalle will have more comments.


> > Wrt. ath9k patches I guess "delegate in patchwork" won't work anymore,
> > but "resend to netdev" or something perhaps?
> 
> We can watch PW state and apply from linux-wireless, I reckon.
> That said I don't know how you use delegation :)

We have auto-delegation set up for this, except iwlwifi is on me right
now for the upstream, and I just delegate other incoming patches to
Gregory.

johannes