From: aspotashev@emcraft.com (Alexander Potashev)
To: linux-arm-kernel@lists.infradead.org
Subject: Renaming MACH_TYPE_KINETIS_K60 into MACH_TYPE_KINETIS
Date: Tue, 03 Jan 2012 20:10:59 +0400 [thread overview]
Message-ID: <1874472.4krplCoJty@myhost> (raw)
In-Reply-To: <20120103153203.GV2914@n2100.arm.linux.org.uk>
On 3 ?????? 2012 15:32:03 Russell King - ARM Linux wrote:
> There's also the issue whether DT on uclinux makes sense as these
> platforms are normally highly focussed and highly embedded (and it
> really doesn't make that much sense to have a single kernel image
> running on all.)
Right. Our workflow is to have a custom kernel image for every particular
embedded system and we are happy with it.
prev parent reply other threads:[~2012-01-03 16:10 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
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 [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=1874472.4krplCoJty@myhost \
--to=aspotashev@emcraft.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 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).