public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: "Eric S. Raymond" <esr@thyrsus.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Missing entries in Configuure.help)
Date: Tue, 8 Jan 2002 19:35:03 +0000	[thread overview]
Message-ID: <20020108193503.GA852@gallifrey> (raw)
In-Reply-To: <20020106210233.A30319@thyrsus.com> <20020107085307.A17914@flint.arm.linux.org.uk> <20020108124334.A24742@thyrsus.com>
In-Reply-To: <20020108124334.A24742@thyrsus.com>

* Eric S. Raymond (esr@thyrsus.com) wrote:

> CPU_ARM922_D_CACHE_ON
> CPU_ARM922_I_CACHE_ON
> CPU_ARM922_WRITETHROUGH

Hmm - is there anything ARM922 specific about these - i.e. is there a
reason that we shouldn't get rid of them and have some architecture
independent symbols CPU_D_CACHE_ON, CPU_I_CACHE_ON and
CPU_CACHE_WRITETHROUGH (and more to your taste) and then architectures
can use the ones which apply to them.

Doesn't seem to be a point in having dupes.

Dave
 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  parent reply	other threads:[~2002-01-08 19:35 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
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 [this message]
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=20020108193503.GA852@gallifrey \
    --to=gilbertd@treblig.org \
    --cc=esr@thyrsus.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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