[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-next
Subject:    Re: Adding modules-linus branch to linux-next
From:       Stephen Rothwell <sfr () canb ! auug ! org ! au>
Date:       2018-04-19 0:02:21
Message-ID: 20180419100221.6e39d072 () canb ! auug ! org ! au
[Download RAW message or body]

Hi Jessica,

On Wed, 18 Apr 2018 22:57:39 +0200 Jessica Yu <jeyu@kernel.org> wrote:
>
> Could you please add the modules-linus branch at:
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git modules-linus
> 
> to linux-next? The branch will contain rc fixes intended for the
> current release. A good name for it might be modules-current.

Added from today.  I called it modules-fixes.

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 #3 (application/pgp-signature)]
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[prev in list] [next in list] [prev in thread] [next in thread]