From: Zach Sadecki <zsadecki@itwatchdogs.com>
To: Huang Shijie <b32955@freescale.com>
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com
Subject: Re: [PATCH] mtd: gpmi: Always report ECC stats and return max_bitflips
Date: Thu, 10 Jan 2013 09:40:33 -0600 [thread overview]
Message-ID: <50EEE0F1.50805@itwatchdogs.com> (raw)
In-Reply-To: <50EE356A.1000108@freescale.com>
On 01/09/2013 09:28 PM, Huang Shijie wrote:
> Dear Zach,
> I think you'd better check the patch with /scripts/checkpatch.pl
> before you send out the patch.
> I saw many "trailing whitespace" in your patch.
>
> thanks.
>
> Huang Shijie
I just checked it:
zach@zpc:~/git/l2-mtd$ scripts/checkpatch.pl
0001-mtd-gpmi-Always-report-ECC-stats-and-return-max_bitf.patch
total: 0 errors, 0 warnings, 59 lines checked
0001-mtd-gpmi-Always-report-ECC-stats-and-return-max_bitf.patch has no
obvious style problems and is ready for submission.
---
The reply to the original thread dated "Thu Dec 13 21:36:43 EST 2012"
should be the correct patch...
Zach
prev parent reply other threads:[~2013-01-10 15:40 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
2013-01-10 3:28 ` Huang Shijie
2013-01-10 15:40 ` Zach Sadecki [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=50EEE0F1.50805@itwatchdogs.com \
--to=zsadecki@itwatchdogs.com \
--cc=b32955@freescale.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