generic-iomap tree for linux-next

Stephen Rothwell sfr at canb.auug.org.au
Thu Nov 7 20:52:48 PST 2019


Hi Christoph,

On Fri, 8 Nov 2019 13:20:00 +1100 Stephen Rothwell <sfr at canb.auug.org.au> wrote:
>
> On Thu, 7 Nov 2019 21:47:43 +0100 Christoph Hellwig <hch at lst.de> wrote:
> >
> > can you add the generic-ioremap tree:
> > 
> >    git://git.infradead.org/users/hch/ioremap.git
> > 
> > to linux-next?   
> 
> I assume you mean the for-next branch?

With that assumption, added from today.

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 at canb.auug.org.au
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20191108/a20d3957/attachment.sig>


More information about the linux-mtd mailing list