From: Artem Bityutskiy <dedekind1@gmail.com>
To: Huang Shijie <b32955@freescale.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 11:34:30 +0300 [thread overview]
Message-ID: <1337589270.2483.66.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FB9FCDE.9070803@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
On Mon, 2012-05-21 at 16:29 +0800, Huang Shijie wrote:
> 于 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()
OK, it is not merged upstream yet, so it does not need the -stable tag.
Thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] GPMI-NAND: Define ecc.strength
Date: Mon, 21 May 2012 11:34:30 +0300 [thread overview]
Message-ID: <1337589270.2483.66.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FB9FCDE.9070803@freescale.com>
On Mon, 2012-05-21 at 16:29 +0800, Huang Shijie wrote:
> ? 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()
OK, it is not merged upstream yet, so it does not need the -stable tag.
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/20120521/1b2f72c8/attachment-0001.sig>
next prev parent reply other threads:[~2012-05-21 8:34 UTC|newest]
Thread overview: 10+ 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 3:44 ` Marek Vasut
2012-05-21 8:13 ` Artem Bityutskiy
2012-05-21 8:13 ` Artem Bityutskiy
2012-05-21 8:29 ` Huang Shijie
2012-05-21 8:29 ` Huang Shijie
2012-05-21 8:34 ` Artem Bityutskiy [this message]
2012-05-21 8:34 ` Artem Bityutskiy
2012-05-21 8:28 ` Huang Shijie
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=1337589270.2483.66.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=b32955@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.