From: Artem Bityutskiy <dedekind1@gmail.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: torvalds@linux-foundation.org,
Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Andrew Morton <akpm@linux-foundation.org>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: No pull for mtd?
Date: Tue, 30 Jul 2013 17:03:54 +0300 [thread overview]
Message-ID: <1375193034.14869.158.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20130731015329.GA2133@gmail.com>
On Tue, 2013-07-30 at 21:53 -0400, Huang Shijie wrote:
> > Well, just go ahead and help.
> >
> > This is also how the l2 tree appeared. I noticed that dwmw2 is becoming
> > slow, and I just went ahead and created this tree without asking him,
> > and told him that now he does not have to go through the mailing list -
> > all the "sane" (from my POW) patches are in the l2 tree.
> >
> > But please, do not create another tree now :-) Either start reviewing
> > others' patches, or declare ownership for some part of MTD and let's
> > create a corresponding branch in my tree for you. E.g., gpmi.
>
> thanks.
>
> But it is no need to create a branch for gpmi. The purely gpmi patches
> are very few. Most of time, the gpmi drives the mtd code to change.
> And the patch set is for both the mtd and the gpmi.
I will start looking at MTD mailing list patches soon and start picking
them. Just back from vacation.
> > In case of Brian, I'd fully trust the entire NAND subsystem to him, he
> > demonstrated that he is capable of taking care of it.
> If Brian acks a patch, and there is no more comment for this patch,
> and you are too busy to review this patch and accept this patch.
> How can this patch be pushed to l2-mtd ?
I'll change my practice and will start processing patches which have
acks from others first.
> This is the exactly situation we are facing now.
>
> If he has the right to push to the l2-mtd tree, i think we can speed up the mtd.
I am fine with giving Brian Norris write rights to the. I trust his
expertise and I like the way communicates and works in the MTD mailing
list.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-07-30 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 12:47 No pull for mtd? Ezequiel Garcia
2013-07-16 2:58 ` Brian Norris
2013-07-17 7:44 ` Huang Shijie
[not found] ` <CAF4G-tLsOO_F-Mhn=+5vS2kkJuoeLJwrTdCR90DVuQQ+xn40aw@mail.gmail.com>
2013-07-17 23:02 ` Brian Norris
2013-07-17 23:13 ` David Woodhouse
2013-07-17 23:26 ` Brian Norris
2013-07-18 1:03 ` David Woodhouse
2013-07-19 5:33 ` Brian Norris
2013-07-20 12:22 ` Huang Shijie
2013-07-30 11:04 ` Artem Bityutskiy
2013-07-31 1:53 ` Huang Shijie
2013-07-30 14:03 ` Artem Bityutskiy [this message]
2013-07-30 15:26 ` Artem Bityutskiy
2013-07-30 21:00 ` Brian Norris
2013-07-31 2:24 ` Huang Shijie
2013-07-30 20:45 ` Brian Norris
2013-07-30 20:33 ` Brian Norris
2013-07-30 10:50 ` Artem Bityutskiy
2013-07-30 10:46 ` 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=1375193034.14869.158.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
--cc=torvalds@linux-foundation.org \
/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