From: "Eric S. Raymond" <esr@thyrsus.com>
To: Philip Blundell <philb@gnu.org>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Re: Configure.help entries wanted
Date: Fri, 25 May 2001 04:04:50 -0400 [thread overview]
Message-ID: <20010525040450.A6265@thyrsus.com> (raw)
In-Reply-To: <20010525012200.A5259@thyrsus.com> <esr@thyrsus.com> <E153C9U-0001op-00@kings-cross.london.uk.eu.org>
In-Reply-To: <E153C9U-0001op-00@kings-cross.london.uk.eu.org>; from philb@gnu.org on Fri, May 25, 2001 at 08:36:52AM +0100
Philip Blundell <philb@gnu.org>:
> >CONFIG_ARCH_FTVPCI
> >CONFIG_ARCH_NEXUSPCI
>
> These symbols both refer to the same thing (the latter is an obsolete name).
> I guess appropriate text would be something like:
>
> Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
> Electronics) StrongARM PCI card.
Hm. They're both in active use in 2.4.5pre4. My cross-referencer shows
CONFIG_ARCH_NEXUSPCI: arch/arm/config.in arch/arm/boot/Makefile arch/arm/kernel/entry-armv.S arch/arm/kernel/arch.c
snark:~/src/linux$ scripts/kxref.py -f "o&~h&~x" -n defconfig | grep FTVPCI
Reading cross-reference database...done.
CONFIG_ARCH_FTVPCI: arch/arm/Makefile arch/arm/config.in arch/arm/boot/compressed/Makefile arch/arm/kernel/Makefile arch/arm/kernel/bios32.c arch/arm/kernel/debug-armv.S arch/arm/def-configs/clps7500 arch/arm/def-configs/shark
On further investigation I find that neither of these symbols is actually
set in the ARM config file! This is kind of a mess. Is it going to be
fixed in the next merge?
(They're not the only dead symbols. CONFIG_TBOX and CONFIG_SHARK don't
have associated questions either.)
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Courage is resistance of fear, mastery of fear, not absence of fear.
next prev parent reply other threads:[~2001-05-25 8:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 5:22 Configure.help entries wanted Eric S. Raymond
2001-05-25 6:03 ` Keith Owens
2001-05-25 6:35 ` Eric S. Raymond
2001-05-25 6:59 ` Keith Owens
2001-05-25 7:10 ` Eric S. Raymond
2001-05-25 7:36 ` Philip Blundell
2001-05-25 8:04 ` Eric S. Raymond [this message]
2001-05-25 10:30 ` [kbuild-devel] " Russell King
2001-05-26 4:34 ` [kbuild-devel] " Greg Banks
2001-05-26 6:06 ` Jaswinder Singh
2001-05-26 10:06 ` Greg Banks
2001-05-26 18:50 ` Jaswinder Singh
2001-05-27 1:12 ` Greg Banks
2001-05-27 1:08 ` Jaswinder Singh
2001-05-27 1:29 ` Greg Banks
2001-05-27 1:28 ` Jaswinder Singh
2001-05-27 2:03 ` Greg Banks
2001-05-27 2:08 ` Jaswinder Singh
2001-05-27 1:20 ` Alan Cox
2001-05-27 1:31 ` Jaswinder Singh
2001-05-27 2:10 ` Greg Banks
2001-05-27 2:13 ` Jaswinder Singh
2001-05-27 2:52 ` Greg Banks
2001-05-27 16:27 ` Pavel Machek
2001-05-28 0:56 ` Greg Banks
2001-05-28 1:05 ` Alan Cox
2001-05-28 2:36 ` Greg Banks
2001-05-28 2:34 ` Jaswinder Singh
2001-05-28 2:58 ` Jaswinder Singh
2001-05-28 3:17 ` Greg Banks
2001-05-27 2:00 ` Greg Banks
2001-05-27 3:06 ` Greg Banks
2001-05-27 3:10 ` Jaswinder Singh
2001-05-27 15:24 ` Greg Banks
2001-05-27 5:03 ` Bill Pringlemeir
2001-05-26 21:48 ` esr
2001-05-27 1:54 ` Jaswinder Singh
2001-05-27 2:43 ` Greg Banks
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=20010525040450.A6265@thyrsus.com \
--to=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=philb@gnu.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