From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MX53: mx53evk: Remove duplicate define
Date: Wed, 11 May 2011 16:38:00 +0200 [thread overview]
Message-ID: <4DCA9F48.6030609@denx.de> (raw)
In-Reply-To: <1305123370-11768-1-git-send-email-fabio.estevam@freescale.com>
On 05/11/2011 04:16 PM, Fabio Estevam wrote:
> Fix the following warning:
>
> ../include/configs/mx53evk.h:195: warning: "CONFIG_OF_LIBFDT" redefined
> ../include/configs/mx53evk.h:41: note: this is the location of the previous definition
>
>
Hi Fabio,
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> include/configs/mx53evk.h | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/include/configs/mx53evk.h b/include/configs/mx53evk.h
> index 5749a08..6ac910b 100644
> --- a/include/configs/mx53evk.h
> +++ b/include/configs/mx53evk.h
> @@ -38,8 +38,6 @@
> #define CONFIG_SETUP_MEMORY_TAGS 1
> #define CONFIG_INITRD_TAG 1
>
> -#define CONFIG_OF_LIBFDT 1
> -
> /* Size of malloc() pool */
> #define CONFIG_SYS_MALLOC_LEN (CONFIG_ENV_SIZE + 2 * 1024 * 1024)
There is already a patch for this:
http://patchwork.ozlabs.org/patch/93978/
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2011-05-11 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 14:16 [U-Boot] [PATCH] MX53: mx53evk: Remove duplicate define Fabio Estevam
2011-05-11 14:38 ` Stefano Babic [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=4DCA9F48.6030609@denx.de \
--to=sbabic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.