xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Cc: Julien Grall <julien.grall@linaro.org>,
	xen-devel@lists.xen.org, stefano.stabellini@eu.citrix.com
Subject: Re: [V2 3/3] amd/seattle: Initial revision of AMD Seattle support
Date: Thu, 2 Oct 2014 22:26:25 +0100	[thread overview]
Message-ID: <1412285185.17796.43.camel@citrix.com> (raw)
In-Reply-To: <542DB775.3030306@amd.com>

On Thu, 2014-10-02 at 15:37 -0500, Suravee Suthikulpanit wrote:
> >>> + * This is temporary until full PSCI-0.2 is supported.
> >>> + * Then, these function will be removed.

> Actually, think about this again, I would rather keep this independent 
> from the other PSCI patch series, which might not make it into 4.5.  It 
> is small enough and probably not too terrible to keep this.

Given the comment about the temporary nature it is IMHO fine to keep
this as is until proper PSCI-0.2 support lands.

Ian.

  reply	other threads:[~2014-10-02 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 19:51 [V2 0/3] Introduce AMD Seattle platform support suravee.suthikulpanit
2014-10-01 19:51 ` [V2 1/3] gicv2: Add compatibility id for gic-400 suravee.suthikulpanit
2014-10-01 19:51 ` [V2 2/3] amd/seattle: Add early printk message for the platform suravee.suthikulpanit
2014-10-02 15:52   ` Julien Grall
2014-10-02 18:40     ` Suravee Suthikulpanit
2014-10-01 19:51 ` [V2 3/3] amd/seattle: Initial revision of AMD Seattle support suravee.suthikulpanit
2014-10-02 10:41   ` Julien Grall
2014-10-02 19:04     ` Suravee Suthikulpanit
2014-10-02 20:37       ` Suravee Suthikulpanit
2014-10-02 21:26         ` Ian Campbell [this message]
2014-10-02 21:44         ` Julien Grall
2014-10-02 12:59 ` [V2 0/3] Introduce AMD Seattle platform support Ian Campbell
2014-10-02 15:10   ` Konrad Rzeszutek Wilk

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=1412285185.17796.43.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).