linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 1/3] MTD : add the common code for GPMI-NAND controller driver
Date: Thu, 8 Sep 2011 09:22:51 +0800	[thread overview]
Message-ID: <4E6818EB.3050907@freescale.com> (raw)
In-Reply-To: <20110907095907.GB1912@pengutronix.de>

Hi,
> On Tue, Sep 06, 2011 at 04:17:08PM +0200, Wolfram Sang wrote:
>>> Should i wait for your test result, and send out the new version v12?
>>> or I send out the new version first, and then you test it again?
>> I'd suggest you send V12 and I will test it when NAND is on my list
>> again. I need to bring up this board first before I can do further
>> testing.
> Maybe you could also remove the debug log level mechanisms? We have
> DYNAMIC_DEBUG to select debug output these days...
>
thanks

Huang Shijie

  reply	other threads:[~2011-09-08  1:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 11:12 [PATCH v11 0/3] add the GPMI controller driver for IMX23/IMX28 Huang Shijie
2011-08-29 11:12 ` [PATCH v11 1/3] MTD : add the common code for GPMI-NAND controller driver Huang Shijie
2011-09-05 15:17   ` Wolfram Sang
2011-09-06  2:00     ` Huang Shijie
2011-09-06 10:31     ` Huang Shijie
2011-09-06 14:17       ` Wolfram Sang
2011-09-07  9:59         ` Wolfram Sang
2011-09-08  1:22           ` Huang Shijie [this message]
2011-08-29 11:13 ` [PATCH v11 2/3] MTD : add helper functions library and header files for GPMI NAND driver Huang Shijie
2011-08-29 11:13 ` [PATCH v11 3/3] MTD : add GPMI-NAND driver in the config and Makefile 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=4E6818EB.3050907@freescale.com \
    --to=b32955@freescale.com \
    --cc=linux-arm-kernel@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 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).