All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <kernel@stabellini.net>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, Julien Grall <julien.grall@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v2] xen/arm64: correctly emulate the {w, x}zr registers
Date: Thu, 24 Mar 2016 11:12:12 +0000	[thread overview]
Message-ID: <56F3CB8C.1090308@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1603241054120.16617@kaball.uk.xensource.com>

(CC committers)

On 24/03/16 10:54, Stefano Stabellini wrote:
> On Wed, 23 Mar 2016, Julien Grall wrote:
>> Hi Stefano,
>>
>> On 22/02/16 17:38, Stefano Stabellini wrote:
>>> On Fri, 15 Jan 2016, Ian Campbell wrote:
>>>
>>> I read the patch and looks good to me. You can add my
>>>
>>> Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>>
>>> I have a couple of minor comments, which you can ignore or address as
>>> you commit the patch.
>>
>> This patch fell through the crack. Some compilers may generate MMIO access
>> with *zr, so we need this patch in Xen 4.7 (and potentially backport it).
>>
>> Are you fine if the patch is not respined?
>
> Yes, I am fine with it as is.

Thanks. Can someone commit this patch?

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-03-24 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 15:17 [PATCH v2] xen/arm64: correctly emulate the {w, x}zr registers Ian Campbell
2016-02-22 17:38 ` Stefano Stabellini
2016-03-23 18:10   ` Julien Grall
2016-03-24 10:54     ` Stefano Stabellini
2016-03-24 11:12       ` Julien Grall [this message]
2016-03-24 11:28         ` Jan Beulich
2016-03-24 11:49           ` 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=56F3CB8C.1090308@arm.com \
    --to=julien.grall@arm.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=kernel@stabellini.net \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@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 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.