From: Alex Williamson <alex.williamson@redhat.com>
To: Alvise Rigo <a.rigo@virtualopensystems.com>
Cc: kvm@vger.kernel.org, eric.auger@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: vfio-platform: Update sub-maintainers
Date: Fri, 23 Mar 2018 13:59:44 -0600 [thread overview]
Message-ID: <20180323135944.54bb75c1@t450s.home> (raw)
In-Reply-To: <20180323175929.15319-1-a.rigo@virtualopensystems.com>
On Fri, 23 Mar 2018 18:59:29 +0100
Alvise Rigo <a.rigo@virtualopensystems.com> wrote:
> Update the sub-maintainer entry as Baptiste has moved.
>
> Add me and Eric Auger as sub-maintainers of the VFIO plaform driver.
>
> Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
> ---
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 73c0cdabf755..9619c41c2316 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14688,7 +14688,8 @@ F: include/linux/mdev.h
> F: samples/vfio-mdev/
>
> VFIO PLATFORM DRIVER
> -M: Baptiste Reynal <b.reynal@virtualopensystems.com>
> +M: Alvise Rigo <a.rigo@virtualopensystems.com>
> +M: Eric Auger <eric.auger@redhat.com>
> L: kvm@vger.kernel.org
> S: Maintained
> F: drivers/vfio/platform/
Hi Alvise,
Thanks for updating this file, I haven't heard from Baptiste for a long
time and I already look to Eric as the de-facto sub-maintainer of vfio
platform. However, I don't have any experience with your reviews, nor
do I see any commits in vfio platform or elsewhere in the kernel
attributed to you. I certainly welcome you on as a designated reviewer
(ie. R:), but I would probably only consider Eric to be the
sub-maintainer at this point. Any objection, Eric? Thanks,
Alex
next prev parent reply other threads:[~2018-03-23 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 17:59 [PATCH] MAINTAINERS: vfio-platform: Update sub-maintainers Alvise Rigo
2018-03-23 19:59 ` Alex Williamson [this message]
2018-03-26 7:11 ` Auger Eric
2018-03-26 8:01 ` Alvise Rigo
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=20180323135944.54bb75c1@t450s.home \
--to=alex.williamson@redhat.com \
--cc=a.rigo@virtualopensystems.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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