[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] make all (native) hypercalls consistently have "long" return type


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Fri, 10 Aug 2012 09:35:24 +0100
  • Cc: dgdegra@xxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Fri, 10 Aug 2012 08:36:21 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac120xXThMBPR6UKQk+2JhXz8/QhwQ==
  • Thread-topic: [Xen-devel] [PATCH] make all (native) hypercalls consistently have "long" return type

On 10/08/2012 08:54, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

>>>> On 10.08.12 at 09:34, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>> On 08/08/2012 17:05, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
>> 
>>> for common and x86 ones at least, to address the problem of storing
>>> zero-extended values into the multicall result field otherwise.
>>> 
>>> Reported-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
>>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
>> 
>> Acked-by: Keir Fraser <keir@xxxxxxx>
>> 
>> Of course this should go in for the next 4.2 RC.
> 
> And I had hoped to also get this into 4.x.y, but I see that you
> tagged the release already (and 4.1 also got pushed from
> staging). So with 4.0.x now presumably dead, I'd just like to
> ask to apply this to 4.1-testing then.

I'm happy to apply it to both, with a 4.x.next-rc1-pre tag. We may never
actually do another release from 4.0 branch however!

Since there's no rush, it can sit in xen-4.2-rc for a short while and then
get backported as part of a batch.

 -- Keir

> Jan
> 



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.