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]

Message-ID: <871qifxm9b.fsf@toke.dk>
Date:   Tue, 13 Jun 2023 20:14:40 +0200
From:   Toke Høiland-Jørgensen <toke@...nel.org>
To:     Kalle Valo <kvalo@...nel.org>, linux-wireless@...r.kernel.org
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev,
        Johannes Berg <johannes@...solutions.net>,
        Jakub Kicinski <kuba@...nel.org>
Subject: Re: Closing down the wireless trees for a summer break?

Kalle Valo <kvalo@...nel.org> writes:

> Me and Johannes are planning to take a longer break from upstream this
> summer. To keep things simple my suggestion is that we would official
> close wireless and wireless-next trees from June 23rd to August 14th
> (approximately).
>
> During that time urgent fixes would need go directly to the net tree.
> Patches can keep flowing to the wireless list but the the net
> maintainers will follow the list and they'll just apply them to the
> net tree directly.
>
> The plan here is that -next patches would have to wait for
> wireless-next to open. Luckily the merge window for v6.6 most likely
> opens beginning of September[1] so after our break we would have few
> weeks to get -next patches ready for v6.6.
>
> And the v6.5 -next patches should be ready by Monday June 19th so that we
> have enough time to get them into the tree before we close the trees.
>
> What do people think, would this work? This is the first time we are
> doing this so we would like to hear any comments about this, both
> negative and positive. You can also reply to me and Johannes privately,
> if that's easier.

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

-Toke