All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lauri Hintsala <lauri.hintsala@bluegiga.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
	mtd <linux-mtd@lists.infradead.org>,
	Subodh Nijsure <snijsure@grid-net.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: GPMI NAND on MX28 with DT.with
Date: Tue, 03 Jul 2012 18:00:48 +0300	[thread overview]
Message-ID: <4FF30920.4010504@bluegiga.com> (raw)
In-Reply-To: <CAMiH66HMCte-8BAqZiPu0T=U9MzCEfyznND0Hwm7TsctzJe9UQ@mail.gmail.com>

Hi Huang

On 06/22/2012 05:45 PM, Huang Shijie wrote:
> Hi,
>    yes, the gpmi-nand has bugs now.
> I will try to fix it when I am free.

Any progress with this? Any ideas what could cause the bug?

Regards,
Lauri Hintsala

WARNING: multiple messages have this Message-ID (diff)
From: lauri.hintsala@bluegiga.com (Lauri Hintsala)
To: linux-arm-kernel@lists.infradead.org
Subject: GPMI NAND on MX28 with DT.with
Date: Tue, 03 Jul 2012 18:00:48 +0300	[thread overview]
Message-ID: <4FF30920.4010504@bluegiga.com> (raw)
In-Reply-To: <CAMiH66HMCte-8BAqZiPu0T=U9MzCEfyznND0Hwm7TsctzJe9UQ@mail.gmail.com>

Hi Huang

On 06/22/2012 05:45 PM, Huang Shijie wrote:
> Hi,
>    yes, the gpmi-nand has bugs now.
> I will try to fix it when I am free.

Any progress with this? Any ideas what could cause the bug?

Regards,
Lauri Hintsala

  reply	other threads:[~2012-07-03 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 22:24 GPMI NAND on MX28 with DT.with Subodh Nijsure
2012-06-21 22:24 ` Subodh Nijsure
2012-06-22 14:45 ` Huang Shijie
2012-06-22 14:45   ` Huang Shijie
2012-07-03 15:00   ` Lauri Hintsala [this message]
2012-07-03 15:00     ` Lauri Hintsala
2012-07-03 15:14     ` Huang Shijie
2012-07-03 15:14       ` Huang Shijie
2012-07-04  5:19       ` Lauri Hintsala
2012-07-04  5:19         ` Lauri Hintsala

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=4FF30920.4010504@bluegiga.com \
    --to=lauri.hintsala@bluegiga.com \
    --cc=b32955@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shijie8@gmail.com \
    --cc=snijsure@grid-net.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.