From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>,
Richard Weinberger <richard@nod.at>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Marek Vasut <marex@denx.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
nicolas.ferre@atmel.com,
Boris Brezillon <boris.brezillon@free-electrons.com>,
LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR subsystem
Date: Wed, 19 Oct 2016 09:41:24 +0300 [thread overview]
Message-ID: <1476859284.18750.115.camel@gmail.com> (raw)
In-Reply-To: <20161018184651.GA71760@google.com>
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.
next prev parent reply other threads:[~2016-10-19 6:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:58 [PATCH 1/1] MAINTAINERS: add a maintainer for the SPI NOR subsystem Cyrille Pitchen
2016-10-18 15:17 ` Marek Vasut
2016-10-18 15:30 ` Richard Weinberger
2016-10-18 15:55 ` Cyrille Pitchen
2016-10-18 16:15 ` Richard Weinberger
2016-10-18 16:37 ` Marek Vasut
2016-10-18 18:46 ` Brian Norris
2016-10-18 19:02 ` Richard Weinberger
2016-10-18 19:15 ` Boris Brezillon
2016-10-18 21:10 ` David Oberhollenzer
2016-10-18 22:04 ` Marek Vasut
2016-10-18 19:31 ` Marek Vasut
2016-10-18 19:41 ` Boris Brezillon
2016-10-18 19:51 ` Marek Vasut
2016-10-19 6:41 ` Artem Bityutskiy [this message]
2016-10-18 19:59 ` Moritz Fischer
2016-10-18 20:18 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476859284.18750.115.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=nicolas.ferre@atmel.com \
--cc=richard@nod.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.