Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1367242 > unrolled thread

Adding the nand/next branch to linux-next

Back to article view | Back to linux.kernel

Contents

  Adding the nand/next branch to linux-next Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-30 16:20 +0200
    Re: Adding the nand/next branch to linux-next Stephen Rothwell <sfr@canb.auug.org.au> - 2016-03-31 00:30 +0200
      Re: Adding the nand/next branch to linux-next Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-31 10:40 +0200

#1367242 — Adding the nand/next branch to linux-next

Hi Stephen,

I recently became maintainer of the NAND flash subsystem, and, if you
don't mind, I'd like to add my nand/next branch [1] to linux-next.

Thanks,

Boris

[1]git://github.com/linux-nand/linux.git nand/next

-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[toc] | [next] | [standalone]

#1367652

Hi Boris,

On Wed, 30 Mar 2016 16:15:38 +0200 Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
>
> I recently became maintainer of the NAND flash subsystem, and, if you
> don't mind, I'd like to add my nand/next branch [1] to linux-next.
> 
> [1]git://github.com/linux-nand/linux.git nand/next

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment 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

[toc] | [prev] | [next] | [standalone]

#1367983

On Thu, 31 Mar 2016 09:24:32 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Boris,
> 
> On Wed, 30 Mar 2016 16:15:38 +0200 Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> >
> > I recently became maintainer of the NAND flash subsystem, and, if you
> > don't mind, I'd like to add my nand/next branch [1] to linux-next.
> > 
> > [1]git://github.com/linux-nand/linux.git nand/next
> 
> Added from today.

Thanks.

> 
> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgment 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.
> 



-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web