From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Renaming MACH_TYPE_KINETIS_K60 into MACH_TYPE_KINETIS
Date: Wed, 28 Dec 2011 18:51:35 +0100 [thread overview]
Message-ID: <201112281851.35717.marek.vasut@gmail.com> (raw)
In-Reply-To: <1325069504.1584.160.camel@skywanderer.emcraft.com>
> On Wed, 2011-12-28 at 11:00 +0100, Marek Vasut wrote:
> > If you use FDT, you won't need machine ID at all.
>
> Hi Marek,
>
> You are right, but we have not used FDT for any of our ARM Linux ports
> yet (consistency matters.) If we switch to FDT now, a lot of code will
> need to be rewritten.
>
> That is why I would prefer to stay with machine type-based
> identification.
Well ... you probably do, let's see about the others ;-)
next prev parent reply other threads:[~2011-12-28 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 9:51 Renaming MACH_TYPE_KINETIS_K60 into MACH_TYPE_KINETIS Alexander Potashev
2011-12-28 10:00 ` Marek Vasut
2011-12-28 10:51 ` Alexander Potashev
2011-12-28 17:51 ` Marek Vasut [this message]
2012-01-01 15:51 ` Rob Herring
2012-01-03 11:03 ` Russell King - ARM Linux
2012-01-03 11:21 ` Alexander Potashev
2012-01-03 15:32 ` Russell King - ARM Linux
2012-01-03 16:10 ` Alexander Potashev
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=201112281851.35717.marek.vasut@gmail.com \
--to=marek.vasut@gmail.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.