All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: dgdegra@tycho.nsa.gov, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] make all (native) hypercalls consistently have "long" return type
Date: Fri, 10 Aug 2012 09:35:24 +0100	[thread overview]
Message-ID: <CC4A865C.3B4E7%keir.xen@gmail.com> (raw)
In-Reply-To: <5024DA61020000780009414F@nat28.tlf.novell.com>

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

>>>> On 10.08.12 at 09:34, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 08/08/2012 17:05, "Jan Beulich" <JBeulich@suse.com> 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@tycho.nsa.gov>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> 
>> Acked-by: Keir Fraser <keir@xen.org>
>> 
>> 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
> 

      reply	other threads:[~2012-08-10  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 16:05 [PATCH] make all (native) hypercalls consistently have "long" return type Jan Beulich
2012-08-10  7:34 ` Keir Fraser
2012-08-10  7:54   ` Jan Beulich
2012-08-10  8:35     ` Keir Fraser [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=CC4A865C.3B4E7%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=dgdegra@tycho.nsa.gov \
    --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.