From: David Gibson <david@gibson.dropbear.id.au>
To: agraf@suse.de
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [0/5] Assorted pseries fixes and updates
Date: Tue, 31 Jul 2012 16:09:00 +1000 [thread overview]
Message-ID: <1343714945-20726-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Hi Alex,
I'm now back from vacation, and have more or less got back on top of
my qemu tree. Here's my first batch of new patches, an assortment of
fairly simple fixes and cleanups for the pseries code.
Please apply.
next reply other threads:[~2012-07-31 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 6:09 David Gibson [this message]
2012-07-31 6:09 ` [Qemu-devel] [PATCH 1/5] pseries: Update SLOF David Gibson
2012-07-31 6:09 ` [Qemu-devel] [PATCH 2/5] pseries: Instantiate USB if requested David Gibson
2012-07-31 7:35 ` Benjamin Herrenschmidt
2012-07-31 7:36 ` Benjamin Herrenschmidt
2012-08-04 7:34 ` Li Zhang
2012-07-31 6:09 ` [Qemu-devel] [PATCH 3/5] pseries: Add support for -vga option David Gibson
2012-07-31 6:09 ` [Qemu-devel] [PATCH 4/5] pseries: Remove extraneous prints David Gibson
2012-07-31 6:09 ` [Qemu-devel] [PATCH 5/5] pseries: Add support for new KVM hash table control call David Gibson
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=1343714945-20726-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--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).