From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Keith Busch <kbusch@kernel.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>
Cc: Klaus Jensen <its@irrelevant.dk>
Subject: Re: [PATCH] MAINTAINERS: update nvme entry
Date: Tue, 7 Jul 2020 08:30:51 +0200 [thread overview]
Message-ID: <105bd6d0-a67b-e8d2-5a13-27e0f5c81472@redhat.com> (raw)
In-Reply-To: <20200706194342.1996219-1-kbusch@kernel.org>
On 7/6/20 9:43 PM, Keith Busch wrote:
> The nvme emulated device development pace has increased recently. Klaus
> has offered to co-maintain, and since we have many new contributions
> coming through, we're adding a repository to accumulate and test new
> features.
Thanks Klaus for helping!
>
> Cc: Klaus Jensen <its@irrelevant.dk>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c31c878c63..fbeba04dc5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1793,10 +1793,12 @@ F: include/hw/virtio/virtio-crypto.h
>
> nvme
> M: Keith Busch <kbusch@kernel.org>
> +M: Klaus Jensen <its@irrelevant.dk>
Is that the correct email you want to use?
Regardless:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> L: qemu-block@nongnu.org
> S: Supported
> F: hw/block/nvme*
> F: tests/qtest/nvme-test.c
> +T: git git://git.infradead.org/qemu-nvme.git nvme-next
>
> megasas
> M: Hannes Reinecke <hare@suse.com>
>
next prev parent reply other threads:[~2020-07-07 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 19:43 [PATCH] MAINTAINERS: update nvme entry Keith Busch
2020-07-07 6:16 ` Klaus Jensen
2020-07-07 6:30 ` Philippe Mathieu-Daudé [this message]
2020-07-07 6:49 ` Klaus Jensen
2020-07-07 15:26 ` Kevin Wolf
2020-07-08 17:03 ` Keith Busch
2020-07-08 17:13 ` Kevin Wolf
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=105bd6d0-a67b-e8d2-5a13-27e0f5c81472@redhat.com \
--to=philmd@redhat.com \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).