From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano.Stabellini@eu.citrix.com, andre.przywara@linaro.org,
patches@linaro.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen/arm: Don't hardcode event channel IRQ
Date: Thu, 30 May 2013 11:50:43 +0100 [thread overview]
Message-ID: <51A72F03.4030107@linaro.org> (raw)
In-Reply-To: <1369901565.13087.19.camel@zakaz.uk.xensource.com>
On 05/30/2013 09:12 AM, Ian Campbell wrote:
> On Mon, 2013-05-20 at 16:58 +0100, Julien Grall wrote:
>> Will be fixed on the next version of the patch.
>
> Did you resend this? If so then I'm afraid I've missed/lost it.
Unfortunately not. I will try to resend it next week.
--
Julien
prev parent reply other threads:[~2013-05-30 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 10:49 [PATCH] xen/arm: Don't hardcode event channel IRQ Julien Grall
2013-05-20 15:32 ` Ian Campbell
2013-05-20 15:58 ` Julien Grall
2013-05-20 16:05 ` Ian Campbell
2013-05-30 8:12 ` Ian Campbell
2013-05-30 10:50 ` 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=51A72F03.4030107@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=andre.przywara@linaro.org \
--cc=patches@linaro.org \
--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).