From: Russell King <rmk@arm.linux.org.uk>
To: "Eric S. Raymond" <esr@thyrsus.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Missing entries in Configuure.help)
Date: Mon, 7 Jan 2002 08:53:07 +0000 [thread overview]
Message-ID: <20020107085307.A17914@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020106210233.A30319@thyrsus.com>
In-Reply-To: <20020106210233.A30319@thyrsus.com>; from esr@thyrsus.com on Sun, Jan 06, 2002 at 09:02:33PM -0500
On Sun, Jan 06, 2002 at 09:02:33PM -0500, Eric S. Raymond wrote:
> 6xx_GENERIC
What's this? Where is it?
> ARCH_CO285
> ARCH_FOOTBRIDGE
> ARCH_SA1100
> ARCH_SHARK
> CPU_ARM922_CPU_IDLE
> CPU_ARM922_D_CACHE_ON
> CPU_ARM922_I_CACHE_ON
> CPU_ARM922_WRITETHROUGH
Erm, I don't believe these have been added since you last complained.
I don't see how they became a non-issue and are now a problem. Please
double-check them.
> ARCH_ADIFCC
> ARCH_AUTCPU12
> ARCH_CAMELOT
> ARCH_CLPS711X
> ARCH_CLPS7500
> ARCH_IOP310
> DEBUG_WAITQ
> DEBUG_LL_SER3
> H3600_SLEEVE
> IOP310_AAU
> IOP310_DMA
> IOP310_MU
> IOP310_PMON
> SA1100_H3100
> SA1100_H3800
> SA1100_PT_SYSTEM3
> SA1100_SHANNON
> SA1100_USB
> SA1100_USB_CHAR
> SA1100_USB_NETLINK
Some of these are waiting to be dug out of my copy of the Configure.help
file and forwarded to Linus.
The only thing I'm doing at the moment is forwarding the stuff that doesn't
touch ARM specific files; Configure.help is a generic file, so it doesn't
get sent as often, and will always take longer (and therefore be out of
date).
next prev parent reply other threads:[~2002-01-07 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 2:02 Missing entries in Configuure.help) Eric S. Raymond
2002-01-07 8:53 ` Russell King [this message]
2002-01-08 17:43 ` Eric S. Raymond
2002-01-08 18:39 ` Greg KH
2002-01-08 18:57 ` Eric S. Raymond
2002-01-08 19:35 ` Dr. David Alan Gilbert
2002-01-08 19:33 ` Eric S. Raymond
2002-01-07 15:56 ` Greg KH
2002-01-08 17:22 ` Eric S. Raymond
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=20020107085307.A17914@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=esr@thyrsus.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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