From: Artem Bityutskiy <dedekind@infradead•org>
To: David Woodhouse <dwmw2@infradead•org>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>,
linux-mtd@lists•infradead.org, devicetree-discuss@ozlabs•org
Subject: Re: [PATCH 1/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Fri, 17 Apr 2009 11:26:18 +0300 [thread overview]
Message-ID: <1239956778.3390.262.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904161936090.12608@baythorne.infradead.org>
On Thu, 2009-04-16 at 19:38 +0100, David Woodhouse wrote:
> On Thu, 16 Apr 2009, Artem Bityutskiy wrote:
>
> > On Thu, 2009-04-16 at 07:46 -0600, Grant Likely wrote:
> >> On Thu, Apr 16, 2009 at 7:37 AM, Stefan Roese <sr@denx•de> wrote:
> >>> On Thursday 16 April 2009, Grant Likely wrote:
> >>>>> Signed-off-by: Stefan Roese <sr@denx•de>
> >>>>> Reviewd-by: Grant Likely <grant.likely@secretlab•ca>
> >>>>
> >>>> Yup, still looks good to me. What boards has this been tested on?
> >>>
> >>> I tested this version on PPC405EX Kilauea equipped only one "standard"
> >>> Spansion S29GL512 NOR chip. And a slightly modified version on an MPC8360
> >>> board (kmeter1) which is equipped with the Intel P30 part mentioned in the
> >>> bindings description. Slightly modified since this board support is not yet
> >>> pushed upstream and currently using v2.6.28 (physmap_of.c has received minor
> >>> modifications after 2.6.28 release).
> >>
> >> Okay. It will be good to get this one into -next for some testing
> >> exposure. Unless he asks me to do otherwise, I'll leave this one to
> >> David to pick up.
> >
> > David usually picks up stuff just before or during merge window,
> > so if you want linux-next exposure, you need to have some extra
> > care.
>
> I don't necessarily do that on purpose; it just works out that way when
> I'm busy.
Yeah, not that I try to blame you, but I think we need to expose stuff
to linux-next. And people who send patches are frustrated when their
stuff gets no attention for very long time.
I understand that MTD tree maintenance is a burden, and you are very
busy, and no one pays you for this job. Thanks for doing it!
I'm going to try to help you. I've just created a git tree where
I'll push patches I consider OK and I approve. Here it is:
git://git.infradead.org/users/dedekind/l2-mtd-2.6.git
My hope is that you would look at that tree from time to time
and pull it. At least you may be sure I looked at the patches and
did some validation. This should save your time and help MTD
users.
Thanks.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-04-17 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 12:10 [PATCH 1/3 v3] mtd: physmap_of: Add multiple regions and concatenation support Stefan Roese
2009-04-16 13:26 ` Grant Likely
2009-04-16 13:37 ` Stefan Roese
2009-04-16 13:46 ` Grant Likely
2009-04-16 13:49 ` Stefan Roese
2009-06-06 3:59 ` Stefan Roese
2009-04-16 13:51 ` Artem Bityutskiy
2009-04-16 14:05 ` Grant Likely
2009-04-16 18:38 ` David Woodhouse
2009-04-17 8:26 ` Artem Bityutskiy [this message]
2009-06-06 7:25 ` David Woodhouse
2009-04-17 12:45 ` Josh Boyer
2009-06-17 5:53 ` Grant Likely
2009-06-23 6:36 ` Stefan Roese
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=1239956778.3390.262.camel@localhost.localdomain \
--to=dedekind@infradead$(echo .)org \
--cc=devicetree-discuss@ozlabs$(echo .)org \
--cc=dwmw2@infradead$(echo .)org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sr@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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