From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: aliguori@us.ibm.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] ppc: Fix bug in handling of PAPR hypercall exits
Date: Wed, 08 Aug 2012 07:03:30 +1000 [thread overview]
Message-ID: <1344373410.2698.17.camel@pasglop> (raw)
In-Reply-To: <49AD223E-F359-4B62-967F-8EABE17D83BE@suse.de>
On Tue, 2012-08-07 at 11:05 +0200, Alexander Graf wrote:
> > This patch therefore changes to ret = 0, which is both a bugfix and a small
> > optimization.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>
> Thanks, applied to ppc-next.
When do you plan to send your queue to Anthony ? Some of that stuff
should be going in ASAP.
Cheers,
Ben.
next prev parent reply other threads:[~2012-08-07 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 4:44 [Qemu-devel] [PATCH] ppc: Fix bug in handling of PAPR hypercall exits David Gibson
2012-08-07 9:05 ` Alexander Graf
2012-08-07 21:03 ` Benjamin Herrenschmidt [this message]
2012-08-07 21:22 ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
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=1344373410.2698.17.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).