From: Wolfgang Denk <wd@denx.de>
To: Dan Malek <dan@embeddededge.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: cleaning up the Kconfig menu structure -- the bigger picture
Date: Sat, 09 Oct 2004 00:03:28 +0200 [thread overview]
Message-ID: <20041008220333.B4276C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 08 Oct 2004 16:49:17 EDT." <85927CE7-196B-11D9-9299-003065F9B7DC@embeddededge.com>
In message <85927CE7-196B-11D9-9299-003065F9B7DC@embeddededge.com> Dan Malek wrote:
>
> I want all of the CPM and 8xx/82xx/85xx configuration to be in
> a common menu, just like it is today. I don't understand the
...
> implement it that way against our wishes. Based upon the
> processor type, we should be invoking different Kconfig
> scripts that although may use the same sources have different
> configuration option criteria. It is significantly easier for
> us to keep those things local for consistent modification,
> and I contend will make it easier to focus on the configuration
> selections when doing so interactively.
Just for the record: I'm 100% in accord with Dan.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Though a program be but three lines long,
someday it will have to be maintained."
- The Tao of Programming
prev parent reply other threads:[~2004-10-08 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 11:16 cleaning up the Kconfig menu structure -- the bigger picture Robert P. J. Day
2004-10-08 15:31 ` Dan Malek
2004-10-08 15:38 ` Robert P. J. Day
2004-10-08 16:37 ` Dan Malek
2004-10-08 16:31 ` Robert P. J. Day
2004-10-08 16:40 ` Tom Rini
2004-10-08 16:42 ` Robert P. J. Day
2004-10-08 17:22 ` Dan Malek
2004-10-08 18:02 ` Tom Rini
2004-10-08 18:39 ` Dan Malek
2004-10-08 19:48 ` Tom Rini
2004-10-08 20:49 ` Dan Malek
2004-10-08 21:38 ` Tom Rini
2004-10-08 22:03 ` Wolfgang Denk [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=20041008220333.B4276C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).