From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Breakage of board ports on new features.
Date: Tue, 05 Dec 2006 11:44:04 -0600 [thread overview]
Message-ID: <4575AFE4.2020108@freescale.com> (raw)
In-Reply-To: <E7593982-8064-4D57-A8D8-83262D2522BA@kernel.crashing.org>
Kumar Gala wrote:
> If the intent is for 'documentation' how about doing:
>
> #define CONFIG_MPC8349 ##
>
> So that if someone uses CONFIG_MPC8349 you can a compile error.
Eh, I don't like that.
I don't think Wolfgang meant to limit CONFIG_MPC8349 to just documentation
purposes. Your idea would require all the board header files to change if
8349-specific is ever introduced.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2006-12-05 17:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 22:08 [U-Boot-Users] Breakage of board ports on new features Pantelis Antoniou
2006-12-02 23:42 ` Wolfgang Denk
2006-12-04 17:32 ` Kumar Gala
2006-12-04 17:54 ` Timur Tabi
2006-12-04 18:40 ` Kumar Gala
2006-12-04 23:09 ` Wolfgang Denk
2006-12-04 23:20 ` Timur Tabi
2006-12-04 23:33 ` Kumar Gala
2006-12-05 1:13 ` Tolunay Orkun
2006-12-05 2:10 ` Kumar Gala
2006-12-05 5:15 ` Tolunay Orkun
2006-12-05 5:32 ` Wolfgang Denk
2006-12-05 14:23 ` Kumar Gala
2006-12-05 15:35 ` Wolfgang Denk
2006-12-05 16:15 ` Kumar Gala
2006-12-05 16:57 ` Wolfgang Denk
2006-12-05 17:42 ` Kumar Gala
2006-12-05 17:44 ` Timur Tabi [this message]
2006-12-05 21:35 ` Wolfgang Denk
2006-12-05 21:50 ` Kumar Gala
2006-12-05 16:36 ` Timur Tabi
2006-12-04 23:08 ` Wolfgang Denk
2006-12-04 16:14 ` Timur Tabi
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=4575AFE4.2020108@freescale.com \
--to=timur@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 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.