From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nathan Williams <nathan@traverse.com.au>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd cs553x_nand: Initialise ecc.strength before nand_scan()
Date: Thu, 22 Nov 2012 13:09:35 +0200 [thread overview]
Message-ID: <1353582575.2701.40.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1353541372.12585.14.camel@laptop>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
On Thu, 2012-11-22 at 10:42 +1100, Nathan Williams wrote:
> Loading cs553x_nand with Hynix H27U1G8F2BTR NAND flash causes this bug:
>
> kernel BUG at drivers/mtd/nand/nand_base.c:3345!
Pushed to l2-mtd.git, added
Cc: stable@vgen.kernel.org [3.4+]
Thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-11-22 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 23:42 [PATCH] mtd cs553x_nand: Initialise ecc.strength before nand_scan() Nathan Williams
2012-11-22 4:08 ` Brian Norris
2012-11-27 18:11 ` Mike Dunn
2012-11-22 11:09 ` Artem Bityutskiy [this message]
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=1353582575.2701.40.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nathan@traverse.com.au \
/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