From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: Keith Busch <kbusch@kernel.org>, Fam Zheng <fam@euphon.net>,
Klaus Jensen <k.jensen@samsung.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: Update nvme entries
Date: Thu, 22 Oct 2020 11:04:24 +0200 [thread overview]
Message-ID: <20201022090424.GA148638@apples.localdomain> (raw)
In-Reply-To: <20201022090045.158261-1-its@irrelevant.dk>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Oct 22 11:00, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Make sure that maintainers of both the nvme block driver and the
> emulated nvme device is notified about changes to the shared nvme.h.
>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6a197bd358d6..f546ac6840f0 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1876,6 +1876,7 @@ M: Klaus Jensen <its@irrelevant.dk>
> L: qemu-block@nongnu.org
> S: Supported
> F: hw/block/nvme*
> +F: include/block/nvme.h
> F: tests/qtest/nvme-test.c
> T: git git://git.infradead.org/qemu-nvme.git nvme-next
>
> @@ -2953,6 +2954,7 @@ R: Fam Zheng <fam@euphon.net>
> L: qemu-block@nongnu.org
> S: Supported
> F: block/nvme*
> +F: include/block/nvme.h
> T: git https://github.com/stefanha/qemu.git block
>
> Bootdevice
> --
> 2.28.0
>
Please diregard. Just realized that Philippe already posted this[1].
So consider this a gentle bump for Philippe's patch to be merged ;)
[1]: https://lore.kernel.org/qemu-devel/20200701140634.25994-1-philmd@redhat.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-22 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 9:00 [PATCH] MAINTAINERS: Update nvme entries Klaus Jensen
2020-10-22 9:04 ` Klaus Jensen [this message]
2020-10-22 15:31 ` Stefan Hajnoczi
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=20201022090424.GA148638@apples.localdomain \
--to=its@irrelevant.dk \
--cc=fam@euphon.net \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=peter.maydell@linaro.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 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).