From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: wireless for-next branches
Date: Sat, 28 May 2022 10:20:53 +1000 [thread overview]
Message-ID: <20220528102053.3733f275@canb.auug.org.au> (raw)
In-Reply-To: <87a6b3qrms.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Hi Kalle,
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-28 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:58 Kalle Valo
2022-05-28 0:20 ` Stephen Rothwell [this message]
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=20220528102053.3733f275@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®