From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Johannes Berg <johannes@sipsolutions•net>
Cc: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel•com>,
Wireless <linux-wireless@vger•kernel.org>,
linux-next@vger•kernel.org
Subject: Re: Introducing iwlwifi-next Tree
Date: Thu, 1 May 2025 08:45:45 +1000 [thread overview]
Message-ID: <20250501084545.2c9de121@canb.auug.org.au> (raw)
In-Reply-To: <2d3c5c2946e4356ba99edb4cca4fa205149c0356.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Hi Johannes,
On Wed, 30 Apr 2025 11:32:37 +0200 Johannes Berg <johannes@sipsolutions•net> wrote:
>
> On Wed, 2025-04-30 at 08:52 +0000, Korenblit, Miriam Rachel wrote:
> > Hi,
> >
> > This is to inform you that a dedicated tree, iwlwifi-next, will be used going forward for development.
> > (instead of wireless/wireless-next)
> >
> > The tree will have 2 branches:
> > 1. fixes – only urgent fix that needs to go to wireless.
> > Patches for this branch should be sent with [PATCH iwlwifi-fixes] in the subject
> > 2. next – all the other patches.
> > Patches for this branch should be sent with [PATCH iwlwifi-next] in the subject
>
> Could you please add this tree to linux-next?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git/
>
> with "next" and "fixes" branches.
Added from today. Currently only you, Johannes, are listed as a
contact for these trees - if you want more added, please let me know.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-30 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW5PR11MB5810F9A009F45F1A58AC0E63A3832@MW5PR11MB5810.namprd11.prod.outlook.com>
2025-04-30 9:32 ` Introducing iwlwifi-next Tree Johannes Berg
2025-04-30 22:45 ` Stephen Rothwell [this message]
2025-05-05 7:56 ` Johannes Berg
2025-05-07 20:37 ` Stephen Rothwell
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=20250501084545.2c9de121@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=johannes@sipsolutions$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=miriam.rachel.korenblit@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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