public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 14:04:08 +0300	[thread overview]
Message-ID: <1375182248.14869.127.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20130720122231.GB4410@gmail.com>

On Sat, 2013-07-20 at 08:22 -0400, Huang Shijie wrote:
> > I think that mostly sounds OK. I can't speak for everyone, but it
> > seems that for some of us, the process just needs to be able to
> adapt
> > to changes in job situations (where at least you and Artem aren't
> even
> > employed in MTD-related work anymore), vacations, babies, absences,
> or
> > any of the other reasons that MTD participation ebbs and flows. So
> > bringing others into the process should help.
> yes.
> 
> If more people can ack and merge the patches, we can speed up the mtd.

Sure. Go ahead and review things which are outside of your gpmi driver.
Ack them, nack them, review them, etc. This will be a real help.
> 
> I really envy the other maillist, you can get response in several
> days.

Well, yes. MTD is a small and (IMHO) a veeery slowly dying subsystem.
People mostly care about their own little things. Few people are
interested in improving it in general. Such is life.

Brian was one of those who did great job in MTD overall, especially in
the NAND framework. He reviewed others patches. But even Brian got
silent lately.

Shmulik comes to mind - he reviewed things all over MTD.

You mostly contribute to your own driver. And I think there were times
when I had to ask you to do an infrastructure rework instead of working
around MTD infrastructure problems with in-driver hacks. No one is
perfect :-)

So there is simply not enough people, thus the slowness.

> > 
> > I guess we'll see what Artem thinks when he's back from vacation and
> Waiting for Artem's solution too. He becomes much busy this year, and
> can not review the patches as he did last year.

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.

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.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2013-07-30 10: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 [this message]
2013-07-31  1:53                     ` Huang Shijie
2013-07-30 14:03                       ` Artem Bityutskiy
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=1375182248.14869.127.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