From: Carsten Schlote <schlote@vahanus.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot refactoring
Date: Fri, 06 Jul 2007 01:53:23 +0200 [thread overview]
Message-ID: <1183679603.3232.1.camel@loki> (raw)
In-Reply-To: <1183661913.26273.49.camel@ld0161-tx32>
Hi,
Am Donnerstag, den 05.07.2007, 13:58 -0500 schrieb Jon Loeliger:
> > With all user-configurable defines starting with CONFIG_ we can start
> > with the rest :-)
>
>
> Say.... Not to put _too_ fine a spin on this, but there
> is a _veeery_ similar issue brewing with the POST CFG_ symbols...
For my kconfig hack in the 1.x tree I to rework both the CONFIG_POST and
CONFIG_COMMAND stuff. Can be solved easily.
Carsten
prev parent reply other threads:[~2007-07-05 23:53 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
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 [this message]
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=1183679603.3232.1.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