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/3] Accumulated ppc patches
Date: Sat, 15 Jun 2013 11:51:49 +1000 [thread overview]
Message-ID: <1371261112-17328-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Hi Alex,
I see that you're now back from your holiday. Here, rather belatedly,
is my series of ppc related patches collected while acting ppc
maintainer. As you can see there aren't many at all. I'm not sure if
that's because I wasn't looking in the right places for people sending
patches, or there just wasn't much activity. Anyway, here they are,
do with them as you see fit.
next reply other threads:[~2013-06-15 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 1:51 David Gibson [this message]
2013-06-15 1:51 ` [Qemu-devel] [PATCH 1/3] target-ppc: Change default machine for 64-bit David Gibson
2013-06-15 1:51 ` [Qemu-devel] [PATCH 2/3] target-ppc kvm: save cr register David Gibson
2013-06-15 1:51 ` [Qemu-devel] [PATCH 3/3] pseries: Update MAINTAINERS information David Gibson
2013-06-18 15:49 ` [Qemu-devel] [0/3] Accumulated ppc patches Alexander Graf
2013-06-18 23:20 ` Alexey Kardashevskiy
2013-06-19 9:41 ` 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=1371261112-17328-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).