From: Alex Williamson <alex.williamson@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <fam@euphon.net>,
philmd@redhat.com
Subject: Re: [PATCH] MAINTAINERS: add Stefan Hajnoczi as block/nvme.c maintainer
Date: Mon, 14 Sep 2020 09:32:35 -0600 [thread overview]
Message-ID: <20200914093235.3777f39b@x1.home> (raw)
In-Reply-To: <20200914103703.GH579094@stefanha-x1.localdomain>
On Mon, 14 Sep 2020 11:37:03 +0100
Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Wed, Sep 09, 2020 at 02:51:50PM +0200, Philippe Mathieu-Daudé wrote:
> > On 9/7/20 1:16 PM, Stefan Hajnoczi wrote:
> > > Development of the userspace NVMe block driver picked up again recently.
> > > After talking with Fam I am stepping up as block/nvme.c maintainer.
> > > Patches will be merged through my 'block' tree.
> > >
> > > Cc: Kevin Wolf <kwolf@redhat.com>
> > > Cc: Klaus Jensen <k.jensen@samsung.com>
> > > Cc: Fam Zheng <fam@euphon.net>
> > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > ---
> > > MAINTAINERS | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index b233da2a73..a143941551 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -2895,10 +2895,12 @@ S: Supported
> > > F: block/null.c
> > >
> > > NVMe Block Driver
> > > -M: Fam Zheng <fam@euphon.net>
> > > +M: Stefan Hajnoczi <stefanha@redhat.com>
> > > +R: Fam Zheng <fam@euphon.net>
> > > L: qemu-block@nongnu.org
> > > S: Supported
> > > F: block/nvme*
> > > +T: git https://github.com/stefanha/qemu.git block
> >
> > As this driver is the only consumer of the 'VFIO helpers',
> > maybe we can:
> >
> > - maintains them in the same bucket
> > - add another entry (eventually with R: tag for Alex)
> >
> > The 'VFIO helpers' files are:
> > - util/vfio-helpers.c
> > - include/qemu/vfio-helpers.h
> >
> > What do you think?
>
> I'm happy to include vfio-helpers with the goal of eventually switching
> to vfio-common.
>
> Alex: does this sound good?
Yep, ok by me. Thanks,
Alex
prev parent reply other threads:[~2020-09-14 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 11:16 [PATCH] MAINTAINERS: add Stefan Hajnoczi as block/nvme.c maintainer Stefan Hajnoczi
2020-09-07 11:33 ` Kevin Wolf
2020-09-07 11:46 ` Klaus Jensen
2020-09-08 8:37 ` Fam Zheng
2020-09-08 14:10 ` Stefan Hajnoczi
2020-09-09 12:51 ` Philippe Mathieu-Daudé
2020-09-14 10:37 ` Stefan Hajnoczi
2020-09-14 15:32 ` Alex Williamson [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=20200914093235.3777f39b@x1.home \
--to=alex.williamson@redhat.com \
--cc=fam@euphon.net \
--cc=k.jensen@samsung.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).