public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: remove NAND_MAX_CHIPS definitions
Date: Thu, 5 Jan 2012 17:41:22 -0600	[thread overview]
Message-ID: <4F063522.8020404@freescale.com> (raw)
In-Reply-To: <1321798216-30283-2-git-send-email-vz@mleia.com>

On 11/20/2011 08:10 AM, Vladimir Zapolskiy wrote:
> This change follows the change by Wolfgang Grandegger (commit 6c869637fef),
> which allows to remove useless NAND_MAX_CHIPS definitions in board config
> files.
> 
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> Cc: Wolfgang Grandegger <wg@grandegger.com>
> Cc: Scott Wood <scottwood@freescale.com>

Applied to u-boot-nand-flash (and a patch coming to get some additional
instances that crept in, plus instances of CONFIG_SYS_NAND_MAX_CHIPS
that are set to the default value of 1).

Marek: this removes NAND_MAX_CHIPS from m28evk.h, which set it to the
non-default value of 8.  This setting was never effective, since
NAND_MAX_CHIPS stopped being used used years before m28evk.h was
introduced.  Does this board want CONFIG_SYS_NAND_MAX_CHIPS = 8?

-Scott

  reply	other threads:[~2012-01-05 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 14:10 [U-Boot] [PATCH] NAND: remove remaining NAND_MAX_CHIPS definitions Vladimir Zapolskiy
2011-11-20 14:10 ` [U-Boot] [PATCH] NAND: remove " Vladimir Zapolskiy
2012-01-05 23:41   ` Scott Wood [this message]
2012-01-06  0:51     ` Marek Vasut
2011-12-06 13:58 ` [U-Boot] [PATCH] NAND: remove remaining " Vladimir Zapolskiy
2011-12-06 17:27   ` Scott Wood
2011-12-06 18:34     ` Vladimir Zapolskiy
2011-12-06 18:56       ` Scott Wood
2011-12-06 19:02         ` Vladimir Zapolskiy

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=4F063522.8020404@freescale.com \
    --to=scottwood@freescale.com \
    --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