From: Huang Shijie <b32955@freescale.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-mtd@lists.infradead.org, Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: nand: gpmi: use correct member for checking NAND_BBT_USE_FLASH
Date: Wed, 1 Feb 2012 10:18:12 +0800 [thread overview]
Message-ID: <4F28A0E4.2020700@freescale.com> (raw)
In-Reply-To: <1328011843-7402-1-git-send-email-w.sang@pengutronix.de>
于 2012年01月31日 20:10, Wolfram Sang 写道:
> This has been moved from .options to .bbt_options meanwhile. So, it
> currently checks for something totally different (NAND_OWN_BUFFERS) and
> decides according to that.
>
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> Cc: Huang Shijie <b32955@freescale.com>
> ---
>
> Artem: NAND_OWN_BUFFERS should not get set, so no danger. But I'd think we
> should add the stable tag nonetheless if Huang is fine with this change.
>
> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> index 493ec2f..f39f83e 100644
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> @@ -1124,7 +1124,7 @@ static int gpmi_block_markbad(struct mtd_info *mtd, loff_t ofs)
> chip->bbt[block >> 2] |= 0x01 << ((block & 0x03) << 1);
>
> /* Do we have a flash based bad block table ? */
> - if (chip->options & NAND_BBT_USE_FLASH)
> + if (chip->bbt_options & NAND_BBT_USE_FLASH)
> ret = nand_update_bbt(mtd, ofs);
> else {
> chipnr = (int)(ofs >> chip->chip_shift);
Acked-by: Huang Shijie <b32955@freescale.com>
I noticed this too.
thanks a lot.
Huang Shijie
next prev parent reply other threads:[~2012-02-01 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 12:10 [PATCH] mtd: nand: gpmi: use correct member for checking NAND_BBT_USE_FLASH Wolfram Sang
2012-01-31 17:42 ` Brian Norris
2012-02-01 2:18 ` Huang Shijie [this message]
2012-02-03 6:30 ` Artem Bityutskiy
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=4F28A0E4.2020700@freescale.com \
--to=b32955@freescale.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=w.sang@pengutronix.de \
/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