From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: linux-mtd@lists.infradead.org, Stefan Roese <sr@denx.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/5] MTD: make MTD_CONCAT support mandatory
Date: Fri, 25 Feb 2011 12:15:37 +0200 [thread overview]
Message-ID: <1298628937.2798.28.camel@localhost> (raw)
In-Reply-To: <AANLkTi=euRE_EsBRrSOsOtNysPT0MpOXQKM-LZ6-07LC@mail.gmail.com>
On Fri, 2011-02-25 at 13:05 +0300, Dmitry Eremin-Solenikov wrote:
> On 2/25/11, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Tue, 2011-02-15 at 17:07 +0300, Dmitry Eremin-Solenikov wrote:
> >> What about this series? Will it find it's way to kernel or should I do
> >> some more steps?
> >
> > They still sit in my l2-mtd-2.6.git tree. You are not expected to do
> > anything, David should look at them an pick them (or reject with an
> > e-mail explaining the reasons) later. Usually he does this closer to the
> > merge window.
>
> Fine, thank you for the explanation. I was just asking because I did not
> know the process behind MTD subsystem.
It should probably be documented. But how it works is that there is
David who is the maintainer. But he is very busy. And there is me who
helps him. I collect patches in my l2 tree. I review those I can and put
my signed-off-by or some other tag. I do not review all patches, and
those I did not review do not have my signed-off-by.
Then at some point David takes a look at my tree and takes patches from
there. If there are patches he dislikes, he usually replies with a
comment and does not take the patch.
So, in your case, the patches are still waiting for his attention. In
the worst case, he picks patches from my tree when the merge window
opens.
> BTW: I've heard the idea about making MTD partitions also a mandatory
> functionality of MTD subsystem. If I make such patches, will stand a chance
> to be accepted, or it's still better to keep MTD parts an option?
In my humble opinion which I think was supported by other people - yes,
the config option is useless and only contributes to mess. I personally
believe we need to kill this.
And I just asked David, he does not mind.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-02-25 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 11:33 [PATCH 1/5] MTD: make MTD_CONCAT support mandatory Dmitry Eremin-Solenikov
2011-01-11 11:33 ` [PATCH 2/5] MTD: drop MTD_CONCAT dependencies from Kconfig Dmitry Eremin-Solenikov
2011-01-11 11:33 ` [PATCH 3/5] MTD: drop CONFIG_MTD_CONCAT ifdefs Dmitry Eremin-Solenikov
2011-01-11 11:33 ` [PATCH 4/5] CRIS: stop checking for MTD_CONCAT Dmitry Eremin-Solenikov
2011-01-12 12:40 ` Jesper Nilsson
2011-01-12 12:41 ` Dmitry Eremin-Solenikov
2011-01-18 11:05 ` Artem Bityutskiy
2011-01-18 14:58 ` Jesper Nilsson
2011-07-09 7:37 ` SV: " Mikael Starvik
2011-01-11 11:33 ` [PATCH 5/5] MTD: drop MTD_CONCAT from Kconfig entirely Dmitry Eremin-Solenikov
2011-01-12 13:25 ` [PATCH 1/5] MTD: make MTD_CONCAT support mandatory Stefan Roese
2011-02-15 14:07 ` Dmitry Eremin-Solenikov
2011-02-25 8:47 ` Artem Bityutskiy
2011-02-25 10:05 ` Dmitry Eremin-Solenikov
2011-02-25 10:15 ` Artem Bityutskiy [this message]
2011-02-25 10:35 ` Artem Bityutskiy
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=1298628937.2798.28.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sr@denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).