From: Huang Shijie <b32955@freescale.com>
To: Florian Fainelli <ffainelli@freebox.fr>
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH] mtd : print out the page size and oob size after parsing out the nand
Date: Wed, 11 Apr 2012 10:01:26 +0800 [thread overview]
Message-ID: <4F84E5F6.7050805@freescale.com> (raw)
In-Reply-To: <4F840B56.403@freebox.fr>
Hi,
> Relying on the kernel to print something to assert the correctness of
> the NAND detection is really weak, you'd better query these properties
> in userland. Also, I am afraid everyone adds a new NAND property
> print-out.
thanks.
If no one like this patch, just ignore it.
Huang Shijie
next prev parent reply other threads:[~2012-04-11 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 3:41 [PATCH] mtd : print out the page size and oob size after parsing out the nand Huang Shijie
2012-04-10 10:28 ` Florian Fainelli
2012-04-11 2:01 ` Huang Shijie [this message]
2012-04-21 14:21 ` Artem Bityutskiy
2012-04-22 5:15 ` Artem Bityutskiy
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=4F84E5F6.7050805@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=ffainelli@freebox.fr \
--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).