From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] is "CONFIG_OMAP_INNOVATOR" a typo or not?
Date: Sat, 21 Nov 2009 02:42:42 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911210238400.29013@localhost> (raw)
in my travels through OMAP land, i'm still running across what look
like typoes but i'm not sure if they are or if there's something
subtle and funky going on underneath with macro concatenation or
something.
witness:
$ grep -r CONFIG.*OMAP.*INNOVATOR *
include/configs/omap1510.h:#ifdef CONFIG_OMAP_INNOVATOR
include/configs/omap1610inn.h:#define CONFIG_MACH_OMAP_INNOVATOR /* Select board mach-type */
include/asm-arm/mach-types.h:#ifdef CONFIG_MACH_OMAP_INNOVATOR
$
so the last two lines above set and test CONFIG_MACH_OMAP_INNOVATOR,
while that first header file instead tests CONFIG_OMAP_INNOVATOR, for
which there is no other reference anywhere else in the tree.
can someone clarify what's happening in cases like that, because
it's not the only example i've run across. thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-11-21 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LFD.2.00.0911210238400.29013@localhost \
--to=rpjday@crashcourse.ca \
--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