From: Alexander Graf <agraf@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: mdroth@linux.vnet.ibm.com, aik@ozlabs.ru, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] Add David Gibson for sPAPR in MAINTAINERS file
Date: Fri, 08 May 2015 02:21:13 +0200 [thread overview]
Message-ID: <554C0179.90309@suse.de> (raw)
In-Reply-To: <1431043860-21428-1-git-send-email-david@gibson.dropbear.id.au>
On 08.05.15 02:11, David Gibson wrote:
> At Alex Graf's request I'm now acting as sub-maintainer for the sPAPR
> (-machine pseries) code. This updates MAINTAINERS accordingly.
>
> While we're at it, change the label to mention pseries since that's the
> actual name of the machine type, even if most of the C files use the sPAPR
> name.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Thanks, applied to ppc-next.
Alex
prev parent reply other threads:[~2015-05-08 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 0:11 [Qemu-devel] [PATCH] Add David Gibson for sPAPR in MAINTAINERS file David Gibson
2015-05-08 0:21 ` Alexander Graf [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=554C0179.90309@suse.de \
--to=agraf@suse.de \
--cc=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=mdroth@linux.vnet.ibm.com \
--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).