linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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:13:11 +0300	[thread overview]
Message-ID: <1337587991.2483.65.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1337571865-8016-1-git-send-email-marex@denx.de>

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?

-- 
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/b4df6bd7/attachment.sig>

  reply	other threads:[~2012-05-21  8:13 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 [this message]
2012-05-21  8:29   ` Huang Shijie
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=1337587991.2483.65.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).