From: Huang Shijie <b32955@freescale.com>
To: <dedekind1@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
Fabio Estevam <fabio.estevam@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] GPMI-NAND: Define ecc.strength
Date: Mon, 21 May 2012 16:29:18 +0800 [thread overview]
Message-ID: <4FB9FCDE.9070803@freescale.com> (raw)
In-Reply-To: <1337587991.2483.65.camel@sauron.fi.intel.com>
于 2012年05月21日 16:13, Artem Bityutskiy 写道:
> On Mon, 2012-05-21 at 05:44 +0200, Marek Vasut wrote:
>> The ecc.strength wasn't set, resulting in the following crash:
> How about ccing -stable? Can you find out which commit broke the driver?
>
The commit cfbc855b (mtd: nand:add sanity check of ecc strength to
nand_scan_tail()
Huang Shijie
next prev parent reply other threads:[~2012-05-21 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 3:44 [PATCH] GPMI-NAND: Define ecc.strength Marek Vasut
2012-05-21 8:13 ` Artem Bityutskiy
2012-05-21 8:29 ` Huang Shijie [this message]
2012-05-21 8:34 ` Artem Bityutskiy
2012-05-21 8:28 ` 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=4FB9FCDE.9070803@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=shawn.guo@linaro.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