From: Sean MacLennan <smaclennan@pikatech.com>
To: "Stefan Roese" <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, sean.maclennan@ottawa.kanatek.ca
Subject: Re: [PATCH] PowerPC 44x: small warp-nand fix
Date: Thu, 5 Jun 2008 22:20:31 -0400 [thread overview]
Message-ID: <20080605222031.1b37eb49@lappy.seanm.ca> (raw)
In-Reply-To: <200806051628.18698.sr@denx.de>
On Thu, 5 Jun 2008 16:28:18 +0200
"Stefan Roese" <sr@denx.de> wrote:
> n Thursday 05 June 2008, Valentine Barshak wrote:
> > The "ndfc-chip" device doesn't need any resources. All resources
> > are handled by the "ndfc-nand" device. Registering the same memory
> > resource twice causes "cat /proc/iomem" to go into an infinite loop
> > displaying NDFC memory addresses.
> >
> > Signed-off-by: Valentine Barshak <vbarshak@ru.mvista.com>
>
> Acked-by: Stefan Roese <sr@denx.de>
Acked-by: Sean MacLennan <smaclennan@pikatech.com>
Cheers,
Sean
prev parent reply other threads:[~2008-06-06 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 13:36 [PATCH] PowerPC 44x: small warp-nand fix Valentine Barshak
2008-06-05 14:28 ` Stefan Roese
2008-06-06 2:20 ` Sean MacLennan [this message]
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=20080605222031.1b37eb49@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sean.maclennan@ottawa.kanatek.ca \
--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).