Subject: Re: Introducing iwlwifi-next Tree

From: Stephen Rothwell <[email-masked]>
Date: Thu, 1 May 2025 08:45:45 +1000

Hi Johannes,

On Wed, 30 Apr 2025 11:32:37 +0200 Johannes Berg <[email-masked]> 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 
[email-masked]