public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch] socfpga: move configuration options to config file
Date: Mon, 20 Apr 2015 23:54:34 +0200	[thread overview]
Message-ID: <20150420215434.GA22618@amd> (raw)
In-Reply-To: <201504202332.33415.marex@denx.de>

On Mon 2015-04-20 23:32:33, Marek Vasut wrote:
> On Monday, April 20, 2015 at 10:27:02 PM, Pavel Machek wrote:
> > On Mon 2015-04-20 21:23:23, Marek Vasut wrote:
> > > On Monday, April 20, 2015 at 02:30:48 PM, Pavel Machek wrote:
> > > > Setting configuration options in header file leads to incosistency
> > > > between .config user sees, and .config he has. What is worse, a lot of
> > > > compile warnings is presented for any such config option user sets in
> > > > .config.
> > > 
> > > Can you please elaborate on such warnings ?
> > 
> > Lets remove CONFIG_CMD_RUN from .config, then select it:
> > 
> > run (CMD_RUN) [N/y/?] (NEW) y
> > 
> > Now you warning for most C files:
> > 
> >   CC      arch/arm/lib/asm-offsets.s
> >   In file included from include/configs/socfpga_cyclone5.h:16:0,
> >                    from include/config.h:5,
> > 		                    from include/common.h:18,
> > 				                     from
> >   arch/arm/lib/asm-offsets.c:15:
> >   include/config_cmd_default.h:38:0: warning: "CONFIG_CMD_RUN"
> >   redefined [enabled by default]
> >    #define CONFIG_CMD_RUN  /* run command in env variable */
> >     ^
> >     In file included from ././include/linux/kconfig.h:4:0,
> >                      from <command-line>:0:
> > 		     include/generated/autoconf.h:35:0: note: this is
> 
> That meant CONFIG_CMD_RUN is defined by default, yes? In which case,
> this patch would just paper over some bug (?) instead of fixing the
> root cause ? The correct fix would probably be to zap those macros,
> which are defined by default from the socfpga_cyclone5.h file, no ?

CONFIG_CMD_RUN is defined in socfpga_cyclone5.h, but it is set to N by
.config. Take a look. If you set it to Y, you'll get the ugly
warnings. Try that.

Apply the patch. See that .config now corresponds to real
configuration and warnings are gone.
									
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-04-20 21:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 12:30 [U-Boot] [patch] socfpga: move configuration options to config file Pavel Machek
2015-04-20 19:23 ` Marek Vasut
2015-04-20 20:27   ` Pavel Machek
2015-04-20 21:32     ` Marek Vasut
2015-04-20 21:54       ` Pavel Machek [this message]
2015-04-21  8:49         ` Marek Vasut
2015-04-21  9:27       ` Masahiro Yamada
2015-04-21  9:23 ` Masahiro Yamada
2015-04-21 10:23   ` [U-Boot] [patchv2] " Pavel Machek
2015-05-15  8:31     ` Pavel Machek
2015-05-15  8:36       ` Masahiro Yamada
2015-05-15  8:48         ` Pavel Machek
2015-05-15  9:00           ` Masahiro Yamada
2015-05-15 11:15             ` Marek Vasut

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=20150420215434.GA22618@amd \
    --to=pavel@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