From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] MAINTAINERS: Add Fam Zheng as Null block driver maintainer
Date: Mon, 30 Mar 2015 06:53:17 -0600 [thread overview]
Message-ID: <5519473D.1020400@redhat.com> (raw)
In-Reply-To: <1427707400-4323-4-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On 03/30/2015 03:23 AM, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> MAINTAINERS | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d7e9ba2..30073a3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1172,6 +1172,12 @@ S: Supported
> F: block/gluster.c
> T: git git://github.com/codyprime/qemu-kvm-jtc.git block
>
> +Null
I wonder if "Null Block Driver" would be any easier to read.
> +M: Fam Zheng <famz@redhat.com>
> +L: qemu-block@nongnu.org
> +S: Supported
> +F: block/null.c
Reviewed-by: Eric Blake <eblake@redhat.com>
> +
> Bootdevice
> M: Gonglei <arei.gonglei@huawei.com>
> S: Maintained
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-03-30 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 9:23 [Qemu-devel] [PATCH 0/3] null driver patches Fam Zheng
2015-03-30 9:23 ` [Qemu-devel] [PATCH 1/3] block/null: Latency simulation by adding new option "latency-ns" Fam Zheng
2015-03-30 9:23 ` [Qemu-devel] [PATCH 2/3] block/null: Support reopen Fam Zheng
2015-03-30 12:54 ` Eric Blake
2015-03-30 9:23 ` [Qemu-devel] [PATCH 3/3] MAINTAINERS: Add Fam Zheng as Null block driver maintainer Fam Zheng
2015-03-30 12:53 ` Eric Blake [this message]
2015-04-01 1:24 ` Fam Zheng
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=5519473D.1020400@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.