From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dimitry Andric <dimitry@andric.com>
Cc: Ben Dooks <ben-linux-arm@fluff.org>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: RFC: rename arch/arm/mach-s3c2410 to arch/arm/mach-s3c24xx
Date: Wed, 19 Apr 2006 16:05:27 +0100 [thread overview]
Message-ID: <20060419150527.GA4102@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4446187C.2090603@andric.com>
On Wed, Apr 19, 2006 at 01:01:16PM +0200, Dimitry Andric wrote:
> Ben Dooks wrote:
> > With the advent of the s3c2410 port adding support for
> > more of the samsung SoC product line (s3c2440, s3c2442,
> > s3c2400) there have been several requests by other people
> > to rename the (in their opinion) increasingly inaccurate
> > arch/arm/mach-s3c2410 to arch/arm/mach-s3c24xx.
>
> Also, I've always found the dichotomy of having
> "include/asm-arm/arch-s3c2410" and "arch/arm/mach-s3c2410" rather weird.
There's a reason for this (this has actually been covered and discussed
at length in the past on the linux-arm mailing lists.)
Folk convinced me that the only thing which we should call "architecture"
is the CPU - so things like "PPC", "ARM", "i386" are architectures, and
not implementations of these (AT91RM9200, S3C2410).
The things in arch/arm/mach* are machine classes which support a variety
of machines which are all essentially similar. Inside these directories
you have the core support for the individual machines.
However, the problem is that we can't rename include/asm-arm/arch-* to
include/asm-arm/mach-*, because we need a symlink to select the right
one. If we renamed include/asm-arm/arch-* to include/asm-arm/mach-*,
we'd want the symlink to be called include/asm-arm/mach.
Unfortunately, we have an include/asm-arm/mach directory, so we'd end
up having to symlink include/asm-arm/mach-* to include/asm-arm/arch.
This would be even more confusing than leaving the include/asm-arm as
currently is.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-04-19 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060418165204.GG2516@trinity.fluff.org>
2006-04-19 11:01 ` Dimitry Andric
2006-04-19 11:20 ` Komal Shah
2006-04-19 14:40 ` Bill Gatliff
2006-04-19 15:05 ` Russell King [this message]
2006-04-20 10:37 ` Andreas Schweigstill
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=20060419150527.GA4102@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=ben-linux-arm@fluff.org \
--cc=dimitry@andric.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
Powered by JetHome