From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add checking the CONFIG_ENV_IS_IN_SPI_FLASH in Enbedded env
Date: Tue, 18 Jan 2011 10:29:12 +0100 [thread overview]
Message-ID: <20110118092912.698A236C@gemini.denx.de> (raw)
In-Reply-To: <4D33C078.3090503@renesas.com>
Dear Yoshihiro Shimoda,
In message <4D33C078.3090503@renesas.com> you wrote:
> Fix the problem which cannot build the U-boot, if we only set
> the CONFIG_ENV_IS_IN_SPI_FLASH.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> ---
> include/environment.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/environment.h b/include/environment.h
> index 082b3e1..8a4f393 100644
> --- a/include/environment.h
> +++ b/include/environment.h
> @@ -106,6 +106,7 @@ extern unsigned long nand_env_oob_offset;
> /* Embedded env is only supported for some flash types */
> #ifdef CONFIG_ENV_IS_EMBEDDED
> # if !defined(CONFIG_ENV_IS_IN_FLASH) && \
> + !defined(CONFIG_ENV_IS_IN_SPI_FLASH) && \
> !defined(CONFIG_ENV_IS_IN_NAND) && \
> !defined(CONFIG_ENV_IS_IN_ONENAND)
Please keep list sorted.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Randal said it would be tough to do in sed. He didn't say he didn't
understand sed. Randal understands sed quite well. Which is why he
uses Perl. :-) - Larry Wall in <7874@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2011-01-18 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 4:07 [U-Boot] [PATCH] add checking the CONFIG_ENV_IS_IN_SPI_FLASH in Enbedded env Yoshihiro Shimoda
2011-01-17 13:09 ` Nobuhiro Iwamatsu
2011-01-18 9:29 ` Wolfgang Denk [this message]
2011-01-19 7:45 ` Yoshihiro Shimoda
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=20110118092912.698A236C@gemini.denx.de \
--to=wd@denx.de \
--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