From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Rodolfo Giometti <giometti@linux.it>
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd pxa3xx_nand.c: add support for 2048 bytes page size layout
Date: Wed, 15 Jan 2014 10:27:25 -0300 [thread overview]
Message-ID: <20140115132724.GB2534@localhost> (raw)
In-Reply-To: <1389623738-19585-1-git-send-email-giometti@linux.it>
Hi Rodolfo,
On Mon, Jan 13, 2014 at 03:35:38PM +0100, Rodolfo Giometti wrote:
> Signed-off-by: Rodolfo Giometti <giometti@linux.it>
> ---
> drivers/mtd/nand/pxa3xx_nand.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
I know this is just a small nitpick, but can you re-submit this
with a subject similar to the other commits:
""mtd: nand: pxa3xx: Add support for 2048 bytes page size devices""
Also, I think you can add some details about the patch in the change
log. Something along these lines might be fine:
""
This commit adds support for devices with 2048B page sizes and
4-bit ECC strength requirements. This is achieved by enabling the BCH
ECC engine, which provides a higher strength: 16-bit over 2048 bytes.
Additionally, add a proper ECC layout to model the controller's view
of the device (where 'U' means unused and 'B' is the bad block marker):
----------------------------------------------------
| 2048B data | B | B | 30B spare | 30B ECC | U | U |
----------------------------------------------------
""
With these modifications you can also add:
Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Thanks a lot for the contribution!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-15 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 14:35 [PATCH] mtd pxa3xx_nand.c: add support for 2048 bytes page size layout Rodolfo Giometti
2014-01-15 13:27 ` Ezequiel Garcia [this message]
2014-01-20 19:24 ` Brian Norris
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=20140115132724.GB2534@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=giometti@linux.it \
--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 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.