From: alexander.stein@systec-electronic.com (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: Machine ID question
Date: Mon, 21 Feb 2011 16:03:05 +0100 [thread overview]
Message-ID: <201102211603.06074.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <20110220130420.GD14495@n2100.arm.linux.org.uk>
On Sunday 20 February 2011, 14:04:20 Russell King - ARM Linux wrote:
> 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.
Ah, without that knowledge Uwe's mail was a bit misleading.
Thanks for clarification.
Alexander
prev parent reply other threads:[~2011-02-21 15:03 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
2011-02-21 14:41 ` John Linn
2011-02-21 15:03 ` Alexander Stein [this message]
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=201102211603.06074.alexander.stein@systec-electronic.com \
--to=alexander.stein@systec-electronic.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.