linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Tabi Timur-B04825 <B04825@freescale.com>,
	Alexander Graf <agraf@suse.de>,
	Gala Kumar-B11780 <B11780@freescale.com>
Subject: Re: RFC: top level compatibles for virtual platforms
Date: Mon, 11 Jul 2011 15:06:12 -0500	[thread overview]
Message-ID: <20110711150612.50f5d75c@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <CACxGe6sRjGzk2iVDXCMZS=AZk8mc_CtGp7CSqnO2WY-yih1Q8A@mail.gmail.com>

On Tue, 12 Jul 2011 04:59:33 +0900
Grant Likely <grant.likely@secretlab.ca> wrote:

> However, compatible values are cheap and while theoretically any
> hypervisor could create a similar machine, the reality is probably
> subtle difference between the implementations.  I'd rather see the
> compatible reflect the specific implementation.

That's what the hypervisor node is for.  We have a tree, let's use it. :-)

-Scott

      reply	other threads:[~2011-07-11 20:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 18:43 RFC: top level compatibles for virtual platforms Yoder Stuart-B08248
2011-07-09  1:39 ` Tabi Timur-B04825
2011-07-09  2:42   ` Grant Likely
2011-07-11 14:36     ` Yoder Stuart-B08248
2011-07-11 14:34   ` Yoder Stuart-B08248
2011-07-11 15:45     ` Timur Tabi
2011-07-11 16:24       ` Scott Wood
2011-07-11 17:41         ` Yoder Stuart-B08248
2011-07-11 18:04           ` Scott Wood
2011-07-11 20:41             ` Yoder Stuart-B08248
2011-07-11 21:06               ` Scott Wood
2011-07-12 14:20                 ` Yoder Stuart-B08248
2011-07-11 17:54         ` Timur Tabi
2011-07-11 19:59     ` Grant Likely
2011-07-11 20:06       ` Scott Wood [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=20110711150612.50f5d75c@schlenkerla.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=B04825@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B11780@freescale.com \
    --cc=agraf@suse.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.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).