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: Re: linux-next: wireless for-next branches
Date: Mon, 30 May 2022 11:54:13 +0300 [thread overview]
Message-ID: <87ilpnpfii.fsf@kernel.org> (raw)
In-Reply-To: <20220528102053.3733f275@canb.auug.org.au> (Stephen Rothwell's message of "Sat, 28 May 2022 10:20:53 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> On Fri, 27 May 2022 11:58:03 +0300 Kalle Valo <kvalo@kernel.org> wrote:
>>
>> 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.
>
> OK, I have switched to using those branches.
Great, thank you Stephen. I now took the first patch[1] to wireless-next
main branch but you should not see it in for-next branch until the merge
window is closed.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/commit/?id=d092de2c28dcf752890252dedefed98f00a631fe
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-05-30 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:58 linux-next: wireless for-next branches Kalle Valo
2022-05-28 0:20 ` Stephen Rothwell
2022-05-30 8:54 ` Kalle Valo [this message]
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=87ilpnpfii.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.