From: jeremy.kerr@canonical.com (Jeremy Kerr)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] [ARM] Introduce 'struct machine_class' for SoC level abstraction
Date: Mon, 21 Jun 2010 15:27:49 +0800 [thread overview]
Message-ID: <201006211527.49786.jeremy.kerr@canonical.com> (raw)
In-Reply-To: <1277042450-30382-1-git-send-email-eric.miao@canonical.com>
Hi Eric,
> For machine class (mostly equivalent to SoC) level abstraction.
Could you detail your intended usage of machine_class and how this will fit in
with the mdesc? Will the mdesc fields override the machine_class fields, or is
this intended to be a replacement?
Cheers,
Jeremy
next prev parent reply other threads:[~2010-06-21 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 14:00 [PATCH 1/2] [ARM] Introduce 'struct machine_class' for SoC level abstraction Eric Miao
2010-06-20 14:00 ` [PATCH 2/2] [ARM] pxa: make use of 'struct machine_class' Eric Miao
2010-06-20 16:08 ` Antonio Ospite
2010-06-21 1:06 ` Eric Miao
2010-06-21 7:27 ` Jeremy Kerr [this message]
2010-06-21 8:23 ` [PATCH 1/2] [ARM] Introduce 'struct machine_class' for SoC level abstraction Eric Miao
2010-06-21 9:02 ` Russell King - ARM Linux
2010-06-21 10:19 ` Eric Miao
2010-06-21 15:38 ` Nicolas Pitre
2010-06-21 15:44 ` Eric Miao
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=201006211527.49786.jeremy.kerr@canonical.com \
--to=jeremy.kerr@canonical.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).