Re: [Ksummit-discuss] bug-introducing patches

From: Stephen Rothwell
Date: Wed May 09 2018 - 17:58:36 EST

Hi Boris,

On Wed, 9 May 2018 21:35:28 +0200 Boris Brezillon <boris.brezillon@xxxxxxxxxxx> wrote:
> I see that the nand/fixes and spi-nor/fixes branch are already there [1].
> You can add:
> mtd-fixes git git://

Added from today.

> You can also remove the mtd entry [2], since mtd-2.6.git is just a sym
> link to linux-mtd.git, so it will just be a duplicate of the mtd-fixes
> entry. You can also rename the l2-mtd entry [3] into mtd.

All done.

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
* submitted under GPL v2 (or later) and include the Contributor's
* 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.

Stephen Rothwell

Attachment: pgpNxxrdRJwGt.pgp
Description: OpenPGP digital signature