From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
zippel@linux-m68k.org, jejb <james.bottomley@steeleye.com>
Subject: Re: how to handle indirect kconfig dependencies
Date: Mon, 20 Nov 2006 19:56:27 +0100 [thread overview]
Message-ID: <4561FA5B.3060702@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061120181319.GX31879@stusta.de>
Adrian Bunk wrote:
> "All of the various shipped tools ... need to be fixed" is a bit
> misleading since one of the features of the 2.6 kconfig is that this
> code is shared by all tools.
All the better, the job will be quickly done then.
--
Stefan Richter
-=====-=-==- =-== =-=--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-11-20 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 4:07 how to handle indirect kconfig dependencies Randy Dunlap
2006-11-17 13:55 ` Stefan Richter
2006-11-20 18:13 ` Adrian Bunk
2006-11-20 18:56 ` Stefan Richter [this message]
2006-11-20 22:09 ` James Bottomley
2006-11-26 3:46 ` Randy Dunlap
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=4561FA5B.3060702@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=bunk@stusta.de \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=zippel@linux-m68k.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