From: Zach Sadecki <zsadecki@itwatchdogs.com>
To: <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: gpmi: Always report ECC stats and return max_bitflips
Date: Thu, 13 Dec 2012 20:39:56 -0600 [thread overview]
Message-ID: <50CA917C.6070408@itwatchdogs.com> (raw)
In-Reply-To: <1355398036.3400.45.camel@sauron.fi.intel.com>
On 12/13/2012 05:27 AM, Artem Bityutskiy wrote:
> On Mon, 2012-12-10 at 09:18 -0600, Zach Sadecki wrote:
>> Always report corrected and failed ECC stats back up to the MTD layer. Also
>> return max_bitflips from read_page() as is expected from NAND drivers now.
>>
>> Signed-off-by: Zach Sadecki <zsadecki@itwatchdogs.com>
>> Acked-by: Huang Shijie <b32955 at freescale.com>
>> ---
> Dunno, may be your patch is corrupted or something. Try to save it and
> apply. This is what I get:
>
> $ git apply --check ~/tmp/zach.mbox
> error: patch failed: drivers/mtd/nand/gpmi-nand/gpmi-nand.c:921
> error: drivers/mtd/nand/gpmi-nand/gpmi-nand.c: patch does not apply
>
> $ git log -1 --oneline
> 70df8b3 mtd: nand: gpmi: reset BCH earlier, too, to avoid NAND startup problems
>
> I've attached the zach.mbox file for you.
>
OK. I rebased the patch on the latest l2-mtd and I tested it with git
apply, so this one should work...
Sent as a separate reply with only the patch in it.
next prev parent reply other threads:[~2012-12-14 2:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 19:48 [PATCH] mtd: gpmi: Always report ECC stats and return max_bitflips Zach Sadecki
2012-12-04 3:34 ` Huang Shijie
2012-12-04 14:40 ` Zach Sadecki
2012-12-05 3:04 ` Huang Shijie
2012-12-10 13:44 ` Artem Bityutskiy
2012-12-10 15:10 ` Zach Sadecki
2012-12-10 15:18 ` Zach Sadecki
2012-12-12 15:17 ` Artem Bityutskiy
2012-12-12 16:57 ` Zach Sadecki
2012-12-13 11:27 ` Artem Bityutskiy
2012-12-14 2:36 ` Zach Sadecki
2012-12-14 2:36 ` Zach Sadecki
2013-01-10 3:01 ` Huang Shijie
2013-01-15 9:30 ` Artem Bityutskiy
2012-12-14 2:39 ` Zach Sadecki [this message]
2013-01-10 3:28 ` Huang Shijie
2013-01-10 15:40 ` Zach Sadecki
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=50CA917C.6070408@itwatchdogs.com \
--to=zsadecki@itwatchdogs.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@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