From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] NAND: Provide a sane default for NAND_MAX_CHIPS.
Date: Thu, 22 May 2008 23:27:42 +0900 [thread overview]
Message-ID: <483582DE.70509@ruby.dti.ne.jp> (raw)
In-Reply-To: <20080519143458.GA24015@ld0162-tx32.am.freescale.net>
Scott Wood wrote:
> This allows the header to be included regardless of whether a board's
> config file provides NAND-related defininitions.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> include/linux/mtd/nand.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
> index 4cc4a7d..e2a25a6 100644
> --- a/include/linux/mtd/nand.h
> +++ b/include/linux/mtd/nand.h
> @@ -385,6 +385,10 @@ struct nand_manufacturers {
> extern struct nand_flash_dev nand_flash_ids[];
> extern struct nand_manufacturers nand_manuf_ids[];
>
> +#ifndef NAND_MAX_CHIPS
> +#define NAND_MAX_CHIPS 8
> +#endif
> +
> /**
> * struct nand_bbt_descr - bad block table descriptor
> * @options: options for this descriptor
Works for me, though I just checked it builds fine.
Acked-by: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
prev parent reply other threads:[~2008-05-22 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 14:34 [U-Boot-Users] [PATCH] NAND: Provide a sane default for NAND_MAX_CHIPS Scott Wood
2008-05-22 14:27 ` Shinya Kuribayashi [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=483582DE.70509@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--cc=u-boot@lists.denx.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