From: Huang Shijie <shijie8@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-arm-kernel@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH 0/4] mtd: gpmi: support two nand chips at most
Date: Sun, 11 Aug 2013 15:52:32 -0400 [thread overview]
Message-ID: <20130811195230.GA28172@gmail.com> (raw)
In-Reply-To: <20130811060921.GB16906@norris.computersforpeace.net>
On Sat, Aug 10, 2013 at 11:09:21PM -0700, Brian Norris wrote:
> On Fri, Jun 14, 2013 at 04:06:21PM +0800, Huang Shijie wrote:
> >
> > drivers/mtd/nand/gpmi-nand/gpmi-lib.c | 14 ++++++++++++++
> > drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 7 +++----
> > drivers/mtd/nand/gpmi-nand/gpmi-regs.h | 3 +++
> > 3 files changed, 20 insertions(+), 4 deletions(-)
>
> What's the status on this patch set? It doesn't look like it got merged.
> Do you have any testing for this? It looks sane enough to me.
Please ignore this patch set. I find a better solution to fix this
issue. I will send a new version of this patch set when it is ready.
thanks
Huang Shijie
WARNING: multiple messages have this Message-ID (diff)
From: shijie8@gmail.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] mtd: gpmi: support two nand chips at most
Date: Sun, 11 Aug 2013 15:52:32 -0400 [thread overview]
Message-ID: <20130811195230.GA28172@gmail.com> (raw)
In-Reply-To: <20130811060921.GB16906@norris.computersforpeace.net>
On Sat, Aug 10, 2013 at 11:09:21PM -0700, Brian Norris wrote:
> On Fri, Jun 14, 2013 at 04:06:21PM +0800, Huang Shijie wrote:
> >
> > drivers/mtd/nand/gpmi-nand/gpmi-lib.c | 14 ++++++++++++++
> > drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 7 +++----
> > drivers/mtd/nand/gpmi-nand/gpmi-regs.h | 3 +++
> > 3 files changed, 20 insertions(+), 4 deletions(-)
>
> What's the status on this patch set? It doesn't look like it got merged.
> Do you have any testing for this? It looks sane enough to me.
Please ignore this patch set. I find a better solution to fix this
issue. I will send a new version of this patch set when it is ready.
thanks
Huang Shijie
next prev parent reply other threads:[~2013-08-11 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 8:06 [PATCH 0/4] mtd: gpmi: support two nand chips at most Huang Shijie
2013-06-14 8:06 ` Huang Shijie
2013-06-14 8:06 ` [PATCH 1/4] mtd: gpmi: decouple the chip select from the DMA channel Huang Shijie
2013-06-14 8:06 ` Huang Shijie
2013-06-14 8:06 ` [PATCH 2/4] mtd: gpmi: use DMA channel 0 for all the nand chips Huang Shijie
2013-06-14 8:06 ` Huang Shijie
2013-06-14 8:06 ` [PATCH 3/4] mtd: gpmi: scan two " Huang Shijie
2013-06-14 8:06 ` Huang Shijie
2013-06-14 8:06 ` [PATCH 4/4] mtd: gpmi: imx6: fix the wrong method for checking ready/busy Huang Shijie
2013-06-14 8:06 ` Huang Shijie
2013-08-11 6:09 ` [PATCH 0/4] mtd: gpmi: support two nand chips at most Brian Norris
2013-08-11 6:09 ` Brian Norris
2013-08-11 19:52 ` Huang Shijie [this message]
2013-08-11 19:52 ` Huang Shijie
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=20130811195230.GA28172@gmail.com \
--to=shijie8@gmail.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.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 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.