xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>,
	tim@xen.org, stefano.stabellini@citrix.com
Subject: Re: [PATCH v3 3/4] xen/xsm: Add support for device tree
Date: Fri, 21 Mar 2014 14:20:59 +0000	[thread overview]
Message-ID: <532C4ACB.9090003@linaro.org> (raw)
In-Reply-To: <1395411176.19839.96.camel@kazak.uk.xensource.com>

Hi Ian,

On 03/21/2014 02:12 PM, Ian Campbell wrote:
> On Fri, 2014-03-21 at 13:05 +0000, Julien Grall wrote:
>> This patch adds a new module "xen,xsm-blob" to allow the user to load the XSM
>> policy when Xen is booting.
> 
> Why "xsm-blob" and not something descriptive like "xsm-policy"?

Actually I didn't though about xsm-policy. Do you mind if I resend only
this patch?

I'm also wondering if I should #ifdef XSM_ENABLE this new part in
common/device_tree.c

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-03-21 14:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 13:05 [PATCH v3 0/4] xen/arm: Add support for XSM Julien Grall
2014-03-21 13:05 ` [PATCH v3 1/4] xen/xsm: Don't use multiboot by default to initialize XSM Julien Grall
2014-03-21 13:05 ` [PATCH v3 2/4] xen/xsm: Add xsm_core_init function Julien Grall
2014-03-21 13:39   ` Jan Beulich
2014-03-21 14:02     ` Julien Grall
2014-03-21 14:46       ` Jan Beulich
2014-03-21 14:16   ` Daniel De Graaf
2014-03-21 13:05 ` [PATCH v3 3/4] xen/xsm: Add support for device tree Julien Grall
2014-03-21 14:12   ` Ian Campbell
2014-03-21 14:20     ` Julien Grall [this message]
2014-03-21 14:21       ` Julien Grall
2014-03-21 15:53         ` Ian Campbell
2014-03-21 13:05 ` [PATCH v3 4/4] xen/arm: Add support for XSM Julien Grall
2014-03-21 13:14   ` Julien Grall

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=532C4ACB.9090003@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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).