From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>, vijay.kilari@gmail.com
Cc: stefano.stabellini@eu.citrix.com,
Prasun.Kapoor@caviumnetworks.com,
vijaya.kumar@caviumnetworks.com, tim@xen.org,
xen-devel@lists.xen.org, stefano.stabellini@citrix.com,
manish.jaggi@caviumnetworks.com
Subject: Re: [PATCH v2 3/3] xen/arm: Skip parsing psci-0.2 from host device tree
Date: Mon, 23 Feb 2015 21:43:29 +0000 [thread overview]
Message-ID: <54EB9F01.7020606@linaro.org> (raw)
In-Reply-To: <1424713947.27930.255.camel@citrix.com>
I think the title of the commit message is misleading.
I gave the impression that we don't want to parse the PSCI-0.2 for Xen,
which is obviously wrong.
A better title would be: "Don't pass the PSCI-0.2 node to the DOM0"
On 23/02/2015 17:52, Ian Campbell wrote:
> On Wed, 2015-02-18 at 17:49 +0530, vijay.kilari@gmail.com wrote:
>> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>>
>> psci node is generated by xen for dom0.
>> if the host device tree has psci-0.2 skip parsing this node
>> and avoid copying from host device tree to dom0 device tree
Missing "." at the end of the sentence.
>>
>> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
> Seems like a candidate for backport to 4.5.
I think so.
Regards,
--
Julien Grall
prev parent reply other threads:[~2015-02-23 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:19 [PATCH v2 0/3] Add ThunderX platform support vijay.kilari
2015-02-18 12:19 ` [PATCH v2 1/3] xen/arm: " vijay.kilari
2015-02-18 12:38 ` Julien Grall
2015-02-23 17:51 ` Ian Campbell
2015-03-03 5:09 ` Vijay Kilari
2015-03-03 9:03 ` Ian Campbell
2015-03-03 9:29 ` Vijay Kilari
2015-03-03 10:18 ` Ian Campbell
2015-02-18 12:19 ` [PATCH v2 2/3] xen/arm: Add early printk support for ThunderX platform vijay.kilari
2015-02-23 17:51 ` Ian Campbell
2015-02-18 12:19 ` [PATCH v2 3/3] xen/arm: Skip parsing psci-0.2 from host device tree vijay.kilari
2015-02-23 17:52 ` Ian Campbell
2015-02-23 21:43 ` Julien Grall [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=54EB9F01.7020606@linaro.org \
--to=julien.grall@linaro.org \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.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 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.