From: Artem Bityutskiy <dedekind@infradead.org>
To: vimal singh <vimalsingh@ti.com>
Cc: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [resending][PATCH] [MTD] [NAND] nand_ecc.c: Bug fix in nand ecc
Date: Wed, 01 Apr 2009 13:01:50 +0300 [thread overview]
Message-ID: <1238580110.20906.73.camel@localhost.localdomain> (raw)
In-Reply-To: <34437.192.168.10.89.1238579632.squirrel@dbdmail.itg.ti.com>
On Wed, 2009-04-01 at 15:23 +0530, vimal singh wrote:
> I do not see this patch on tree, yet.
>
> ------------------------------ Original Message -------------------------------
> Subject: [PATCH] [MTD] [NAND] nand_ecc.c: Bug fix in nand ecc
> From: "vimal singh" <vimalsingh@ti.com>
> Date: Mon, February 23, 2009 1:46 pm
> To: linux-mtd@lists.infradead.org
> -------------------------------------------------------------------------------
>
> Type of 'byte_addr' needed to change for 512 byte ecc support.
>
> Signed-off-by: Vimal Singh <vimalsingh@ti.com>
Probably because you did not try to CC the author of the
code and get his ack. Isn't this logical step to do?
I've CCed Frams.
> ---
>
> diff --git a/drivers/mtd/nand/nand_ecc.c b/drivers/mtd/nand/nand_ecc.c index
> 868147a..6b19058 100644
> --- a/drivers/mtd/nand/nand_ecc.c
> +++ b/drivers/mtd/nand/nand_ecc.c
> @@ -429,7 +429,8 @@ int nand_correct_data(struct mtd_info *mtd, unsigned char
> *buf,
> unsigned char *read_ecc, unsigned char *calc_ecc)
> {
> unsigned char b0, b1, b2;
> - unsigned char byte_addr, bit_addr;
> + uint32_t byte_addr;
> + unsigned char bit_addr;
> /* 256 or 512 bytes/ecc */
> const uint32_t eccsize_mult =
> (((struct nand_chip *)mtd->priv)->ecc.size) >> 8;
>
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-04-01 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 9:53 [resending][PATCH] [MTD] [NAND] nand_ecc.c: Bug fix in nand ecc vimal singh
2009-04-01 10:01 ` Artem Bityutskiy [this message]
2009-04-01 10:02 ` Artem Bityutskiy
2009-04-01 10:11 ` Singh, Vimal
2009-04-24 6:32 ` Singh, Vimal
2009-04-24 7:39 ` Artem Bityutskiy
2009-04-24 8:27 ` Singh, Vimal
2009-04-24 9:31 ` Artem Bityutskiy
2009-04-25 14:55 ` Frans Meulenbroeks
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=1238580110.20906.73.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=fransmeulenbroeks@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vimalsingh@ti.com \
/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