linux-kernel - linux-next: wireless for-next branches

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-next>] [day] [month] [year] [list]

Date:   Fri, 27 May 2022 11:58:03 +0300
From:   Kalle Valo <kvalo@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: linux-next: wireless for-next branches

Hi Stephen,

We are experimenting how we could take "next-next" patches during merge
windows and avoid accumulation of patches for the period which is in
practice three weeks for wireless patches. To do that could you please
change linux-next to pull from wireless trees for-next branches instead
of main branches? So the new locations are:

git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git for-next
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git for-next

The idea we have is that wireless-next for-next branch is not updated
during the merge window and then the "next-next" patches will not be
included in linux-next until the merge window has closed.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches