From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] include/autoconf.mk issue
Date: Thu, 20 Mar 2008 10:38:06 -0500 [thread overview]
Message-ID: <1206027486.5488.25.camel@ld0161-tx32> (raw)
In-Reply-To: <20080320153230.3062524A8B@gemini.denx.de>
On Thu, 2008-03-20 at 10:32, Wolfgang Denk wrote:
> Um... that would fix this specific situation - but we might still run
> into the same problem with the next attempt to convert code to the
> new config style.
Yeah, we just need to pick 'em off one-by-one... :-)
> For example, there might be code which might be compiled depending on
> CONFIG_PREBOOT.
Ah, as I understand that one, I think it gets solved in
a slightly different manner. The kernel introduces a "HAS"
variant that indicates if the feature is enabled and
then uses something like CONFIG_HAS_PREBOOT to indicate
and test for its presence. The actual _value_ remains
the CONFIG_PREBOOT symbol.
jdl
next prev parent reply other threads:[~2008-03-20 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 23:29 [U-Boot-Users] include/autoconf.mk issue Wolfgang Denk
2008-03-20 14:46 ` Jon Loeliger
2008-03-20 15:32 ` Wolfgang Denk
2008-03-20 15:38 ` Jon Loeliger [this message]
2008-03-20 16:02 ` Wolfgang Denk
2008-03-20 16:41 ` Jerry Van Baren
2008-03-20 21:50 ` Grant Likely
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=1206027486.5488.25.camel@ld0161-tx32 \
--to=jdl@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