linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH V2 0/4] mtd: gpmi: support two nand chips at most
Date: Mon, 21 Oct 2013 11:40:16 +0800	[thread overview]
Message-ID: <5264A220.2070900@freescale.com> (raw)
In-Reply-To: <CAN8TOE8xDdRF4Hf+p4JMAixWfkxkbKCZB-fqpPA6yiMHYm=Qew@mail.gmail.com>

于 2013年10月19日 10:01, Brian Norris 写道:
> Yes, I seem to have overlooked this set. I think it must have come in
> parallel with your MLC patch set, so I delayed it until the MLC patch
> set settled down?
>
this patch set has no relationship with MLC patch.

> Anyway, I'll revisit this soon. But I probably need to take care of
> your mtd-utils updates first, since they should go along with the MLC
> patch set.
>
> And on top of that (to update the world on daily status), I seem to be
> tripping over some UBIFS bugs that are inhibiting the validation I'm
> trying to do for some new hardware. So, I'm all-around pretty busy!
> I'll get myself together next week, hopefully.
understood.


I am too busy too, i am starting to code the Qspi driver now.
I was blocked by a bluetooth/uart/dma issue last month.
> In the meantime, other people's code could use some extra eyes. I know
> Ezequiel just sent out a 27 (!) patch series today. There's also the
> pending cmdline.c patch from months ago, where Cai Zhiyong wanted to
> migrate our command line partition parser to a common
> block/cmdline-parser.c. Part of her work (for block devices) is
I like Cai zhiyong's patch. But I do not have time to test his patch.


thanks
Huang Shijie

  reply	other threads:[~2013-10-21  3:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  9:29 [PATCH V2 0/4] mtd: gpmi: support two nand chips at most Huang Shijie
2013-08-27  9:29 ` [PATCH V2 1/4] mtd: gpmi: decouple the chip select from the DMA channel Huang Shijie
2013-08-27  9:29 ` [PATCH V2 2/4] mtd: gpmi: use DMA channel 0 for all the nand chips Huang Shijie
2013-08-27 17:05   ` Vikram Narayanan
2013-08-28  2:19     ` Huang Shijie
2013-08-27  9:29 ` [PATCH V2 3/4] mtd: gpmi: scan two " Huang Shijie
2013-08-27  9:29 ` [PATCH V2 4/4] mtd: gpmi: imx6: fix the wrong method for checking ready/busy Huang Shijie
2013-09-25  2:45 ` [PATCH V2 0/4] mtd: gpmi: support two nand chips at most Huang Shijie
2013-10-18  6:50 ` Huang Shijie
2013-10-19  2:01   ` Brian Norris
2013-10-21  3:40     ` Huang Shijie [this message]
2013-10-21  6:01       ` Gupta, Pekon
2013-10-21  8:32         ` Huang Shijie
2013-10-21  9:02           ` Gupta, Pekon
2013-10-22  8:16             ` Huang Shijie
2013-10-22  8:34               ` Sourav Poddar
2013-10-22  9:03                 ` Huang Shijie
2013-10-23 22:37       ` Brian Norris
2013-10-23 22:59 ` Brian Norris

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=5264A220.2070900@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@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 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).