From: Grant Likely <grant.likely@secretlab.ca>
To: dedekind@infradead.org
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
devicetree-discuss@ozlabs.org
Subject: Re: [PATCH 1/3 v3] mtd: physmap_of: Add multiple regions and concatenation support
Date: Thu, 16 Apr 2009 08:05:38 -0600 [thread overview]
Message-ID: <fa686aa40904160705x432affadw4eb921aa3ea8f07e@mail.gmail.com> (raw)
In-Reply-To: <1239889899.3390.216.camel@localhost.localdomain>
On Thu, Apr 16, 2009 at 7:51 AM, Artem Bityutskiy
<dedekind@infradead.org> 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.
Okay, thanks.
David, I'd like to get this into a -next tree. Are you okay with it
going in via the powerpc tree?
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-04-16 14:05 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
[not found] ` <1239883845-17804-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2009-04-16 13:26 ` Grant Likely
[not found] ` <fa686aa40904160626k118cea3cvc0db38a2277e45b8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-16 13:37 ` Stefan Roese
2009-04-16 13:46 ` Grant Likely
[not found] ` <fa686aa40904160646v75a98e02s446fd89c08cfebae-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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 [this message]
2009-04-16 18:38 ` David Woodhouse
2009-04-17 8:26 ` Artem Bityutskiy
[not found] ` <1239956778.3390.262.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-06-06 7:25 ` David Woodhouse
2009-04-17 12:45 ` Josh Boyer
2009-06-17 5:53 ` Grant Likely
[not found] ` <fa686aa40906162253j76776e88y9d7c818f4d0f1508-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=fa686aa40904160705x432affadw4eb921aa3ea8f07e@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dedekind@infradead.org \
--cc=devicetree-discuss@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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