From: Kalle Valo <kvalo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: wireless for-next branches
Date: Fri, 27 May 2022 11:58:03 +0300 [thread overview]
Message-ID: <87a6b3qrms.fsf@kernel.org> (raw)
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
next reply other threads:[~2022-05-27 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:58 Kalle Valo [this message]
2022-05-28 0:20 ` linux-next: wireless for-next branches Stephen Rothwell
2022-05-30 8:54 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6b3qrms.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox