From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2] onenand: Fix compile errors due to FlexOneNAND
Date: Wed, 6 Jan 2010 16:30:25 -0600 [thread overview]
Message-ID: <20100106223025.GB28859@loki.buserror.net> (raw)
In-Reply-To: <4B2B8C07.4030908@windriver.com>
On Fri, Dec 18, 2009 at 08:04:55AM -0600, Tom wrote:
> Sanjeev Premi wrote:
> > This patch fixes the compile error while trying to
> > compile for omap3evm.
> >
> > env_onenand.c: In function 'env_relocate_spec':
> > env_onenand.c:70: error: 'CONFIG_ENV_ADDR_FLEX' undeclared
> > (first use in this function)
> > env_onenand.c:70: error: (Each undeclared identifier is re
> > ported only once
> > env_onenand.c:70: error: for each function it appears in.)
> > env_onenand.c: In function 'saveenv':
> > env_onenand.c:106: error: 'CONFIG_ENV_ADDR_FLEX' undeclare
> > d (first use in this function)
> > env_onenand.c:107: error: 'CONFIG_ENV_SIZE_FLEX' undeclare
> > d (first use in this function)
> >
> > Signed-off-by: Sanjeev Premi <premi@ti.com>
>
> Ack-ed
> Thank you,
> Tom
Applied to u-boot-nand-flash.
-Scott
prev parent reply other threads:[~2010-01-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 9:25 [U-Boot] [PATCHv2] onenand: Fix compile errors due to FlexOneNAND Sanjeev Premi
2009-12-18 14:04 ` Tom
2010-01-06 22:30 ` Scott Wood [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=20100106223025.GB28859@loki.buserror.net \
--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