From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Machine ID question
Date: Sun, 20 Feb 2011 13:04:20 +0000 [thread overview]
Message-ID: <20110220130420.GD14495@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201102141612.17340.alexander.stein@systec-electronic.com>
On Mon, Feb 14, 2011 at 04:12:16PM +0100, Alexander Stein wrote:
> On Thursday 10 February 2011, 09:29:15 Uwe Kleine-K?nig wrote:
> > On Wed, Feb 09, 2011 at 02:23:07PM -0700, John Linn wrote:
> > > I used the form to create a new machine ID for the new Xilinx platform
> > > in anticipation of
> > > the code making it into the mainline sometime in the future.
> > >
> > > The proposed patches are using ARCH_XILINX in the Kconfig.
> >
> > You should use MACH_XILINX in the patches. There are some ARCH_... in
> > the machine db, but I think nowadays you cannot (and should not) create
> > them there.
>
> Uhm, the last entry in the db was created today (14th Feb). Is there a reason
> why there no new entries should be created?
huh?
The machine registry hands out MACH_foo identifiers. It used to hand
them out as ARCH_foo identifiers, but we decided that was misleading -
it's dealing with machines, not architectures. So a MACH_ prefix is
more correct than an ARCH_ prefix.
next prev parent reply other threads:[~2011-02-20 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 21:23 Machine ID question John Linn
2011-02-10 8:29 ` Uwe Kleine-König
2011-02-14 14:46 ` John Linn
2011-02-14 15:12 ` Alexander Stein
2011-02-20 13:04 ` Russell King - ARM Linux [this message]
2011-02-21 14:41 ` John Linn
2011-02-21 15:03 ` Alexander Stein
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=20110220130420.GD14495@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).