From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] GPMI-NAND: Define ecc.strength
Date: Tue, 22 May 2012 09:33:03 +0300 [thread overview]
Message-ID: <1337668383.2483.87.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1337633967-8387-1-git-send-email-marex@denx.de>
On Mon, 2012-05-21 at 22:59 +0200, Marek Vasut wrote:
> The ecc.strength wasn't set, resulting in the following crash:
> [ 2.550000] kernel BUG at drivers/mtd/nand/nand_base.c:3347!
> [ 2.550000] Internal error: Oops - BUG: 0 [#1] ARM
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120522/03e8cb1d/attachment.sig>
next prev parent reply other threads:[~2012-05-22 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 20:59 [PATCH V2] GPMI-NAND: Define ecc.strength Marek Vasut
2012-05-22 2:12 ` Huang Shijie
2012-05-22 6:33 ` Artem Bityutskiy [this message]
2012-05-22 6:34 ` Marek Vasut
2012-05-24 15:46 ` Mike Dunn
2012-05-24 21:27 ` Marek Vasut
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=1337668383.2483.87.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@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).