From: Carsten Schlote <schlote@vahanus.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot refactoring
Date: Wed, 04 Jul 2007 21:11:46 +0200 [thread overview]
Message-ID: <1183576307.3393.38.camel@loki> (raw)
In-Reply-To: <fa686aa40707031148x4e5508ebgac2268741ee98b2e@mail.gmail.com>
Hi Grant,
> each invasive change. Thoughts? I also think that Jon's CONFIG_
> changes should probably be merged first, and as soon as possible.
Yes, these CFG_ defines are real show blockers. Getting rid of them in
all board headers could really simplify the integration of kconfig.
CFG_ defines can be everywhere else in the source, as long as they are
non defined or changed by a user.
With all user-configurable defines starting with CONFIG_ we can start
with the rest :-)
Regards
Carsten
next prev parent reply other threads:[~2007-07-04 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 18:48 [U-Boot-Users] U-boot refactoring Grant Likely
2007-07-03 21:04 ` Wolfgang Denk
2007-07-03 21:19 ` Jon Loeliger
2007-07-03 21:40 ` Wolfgang Denk
2007-07-03 22:00 ` Jon Loeliger
2007-07-03 22:44 ` Wolfgang Denk
2007-07-04 18:15 ` Jon Loeliger
2007-07-04 8:20 ` Robert Schwebel
2007-07-04 13:44 ` Wolfgang Denk
2007-07-04 19:11 ` Carsten Schlote [this message]
2007-07-05 18:58 ` Jon Loeliger
2007-07-05 20:09 ` Wolfgang Denk
2007-07-05 20:29 ` Jon Loeliger
2007-07-05 23:53 ` Carsten Schlote
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=1183576307.3393.38.camel@loki \
--to=schlote@vahanus.net \
--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