[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1476859284.18750.115.camel@gmail.com>
Date: Wed, 19 Oct 2016 09:41:24 +0300
From: Artem Bityutskiy <dedekind1@...il.com>
To: Brian Norris <computersforpeace@...il.com>,
Richard Weinberger <richard@....at>
Cc: Cyrille Pitchen <cyrille.pitchen@...el.com>,
Marek Vasut <marex@...x.de>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
nicolas.ferre@...el.com,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
LKML <linux-kernel@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR
subsystem
On Tue, 2016-10-18 at 11:46 -0700, Brian Norris wrote:
> I could go with either method I suppose, but I don't personally like
> the
> idea of splitting out the various bits of MTD into *completely*
> independent lines of development. As long as someone (not necessarily
> me) can manage pulling the sub-subsystems together, I think it would
> make sense to have 1 PR for Linus for non-UBI/FS MTD changes.
I think this is a good point. MTD is pretty much a "don't care"
subsystem for Linus, an I do not think he'll appreciate 2 or more micro
MTD pull requests. It makes a lot more sense to consolidate all this
under a single tree MTD tree and make a single pull request.
Powered by blists - more mailing lists