From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] make all (native) hypercalls consistently have "long" return type Date: Fri, 10 Aug 2012 09:35:24 +0100 Message-ID: References: <5024DA61020000780009414F@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5024DA61020000780009414F@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: dgdegra@tycho.nsa.gov, xen-devel List-Id: xen-devel@lists.xenproject.org On 10/08/2012 08:54, "Jan Beulich" wrote: >>>> On 10.08.12 at 09:34, Keir Fraser wrote: >> On 08/08/2012 17:05, "Jan Beulich" 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 >>> Signed-off-by: Jan Beulich >> >> Acked-by: Keir Fraser >> >> 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 >