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-kernel@vger.kernel.org, dedekind1@gmail.com
Subject: Re: [PATCH v2 4/4] mtd: gpmi: update the ecc step size for mtd_info{}
Date: Sun, 11 Aug 2013 11:07:51 -0400 [thread overview]
Message-ID: <5207A8C7.4050101@gmail.com> (raw)
In-Reply-To: <CAN8TOE8NhcYBP_x26=KC2yBUSS3xzVjMg+PHnxNNRNJWWLeSeg@mail.gmail.com>
于 2013年08月10日 03:53, Brian Norris 写道:
> The right way seems to be to avoid nand_scan() directly but instead to
> > use nand_scan_ident() and nand_scan_tail() separately (that's what
> > they're exported for) so that you can initialize any geometry-related
> > options before nand_scan_tail() does the last steps.
i agree with you.
I will create a v3 version tomorrow when i back to office.
thanks for the review.
Huang Shijie
next prev parent reply other threads:[~2013-08-11 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 8:46 [PATCH v2 0/4] Export the ecc step size to user applications Huang Shijie
2013-05-15 8:46 ` [PATCH v2 1/4] mtd: add a new field to mtd_info{} Huang Shijie
2013-05-15 8:46 ` [PATCH v2 2/4] mtd: add a new sys node to show the ecc step size Huang Shijie
2013-08-10 7:15 ` Brian Norris
2013-05-15 8:46 ` [PATCH v2 3/4] mtd: set the ecc step size for master/slave mtd_info Huang Shijie
2013-05-15 8:46 ` [PATCH v2 4/4] mtd: gpmi: update the ecc step size for mtd_info{} Huang Shijie
2013-08-10 7:41 ` Brian Norris
2013-08-10 7:53 ` Brian Norris
2013-08-11 15:07 ` Huang Shijie [this message]
2013-05-15 12:07 ` [PATCH v2 0/4] Export the ecc step size to user applications Artem Bityutskiy
2013-05-16 4:09 ` [PATCH v2 append] mtd: update the ABI document about the ecc step Huang Shijie
2013-08-10 8:20 ` Brian Norris
[not found] ` <CAMiH66GygmwvfZrwys7RoeoY4Q_fFkfbiZF_pJN4RxQBPaz0fw@mail.gmail.com>
2013-05-16 7:19 ` [PATCH v2 0/4] Export the ecc step size to user applications Artem Bityutskiy
2013-05-16 8:10 ` Huang Shijie
2013-08-08 8:37 ` 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=5207A8C7.4050101@gmail.com \
--to=shijie8@gmail.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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