From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mj Embd <mj.embd@gmail.com>
Cc: Julien Grall <julien.grall@linaro.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM GIC Security Extensions and Xen
Date: Thu, 31 Oct 2013 16:14:24 +0000 [thread overview]
Message-ID: <1383236064.25018.125.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CAPUj1OOpy4rLSOMCBs6UkTL57rrBt5AY4jvcyGz5yFd0be6joA@mail.gmail.com>
On Thu, 2013-10-31 at 00:23 +0530, Mj Embd wrote:
> I have just sent with a more descriptive question with subject :
>
> [query] gic_set_lr always uses maintenance Interrupt
I think I replied to this one this afternoon. Let me know if that was
something different.
For future discussions can you please avoid top-posting.
Thanks.
Ian.
next prev parent reply other threads:[~2013-10-31 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 11:27 ARM GIC Security Extensions and Xen Mj Embd
2013-10-28 11:29 ` Mj Embd
2013-10-28 15:00 ` Julien Grall
2013-10-29 14:14 ` Mj Embd
2013-10-30 18:51 ` Julien Grall
2013-10-30 18:53 ` Mj Embd
2013-10-31 16:14 ` Ian Campbell [this message]
2013-10-31 16:49 ` Mj Embd
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=1383236064.25018.125.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=mj.embd@gmail.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).