From: Yuanhan Liu <yliu@fridaylinux.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Tan Jianfeng <jianfeng.tan@intel.com>,
Tiwei Bie <tiwei.bie@intel.com>,
techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] MAINTAINERS: resign from vhost/virtio maintainer
Date: Mon, 12 Feb 2018 19:40:51 +0800 [thread overview]
Message-ID: <20180212114051.GB2156@yliu-mob> (raw)
In-Reply-To: <fd2b8966-d4a7-dba8-6386-3390f113cb07@redhat.com>
On Mon, Feb 12, 2018 at 10:54:08AM +0100, Maxime Coquelin wrote:
> Hi Yuanhan,
>
> On 02/12/2018 10:44 AM, Yuanhan Liu wrote:
> >On Mon, Feb 12, 2018 at 04:51:58PM +0800, Yuanhan Liu wrote:
> >>I was doing terrible reviews jobs recently, and to not hold back
> >>the vhost/virtio development, it's better for me to resign.
>
> I would not put this in the commit message, because even you had less
> time to review vhost/virtio patches recently, you have done a great work
> on maintaining virtio and vhost generally, we owe you a lot of thanks
> for this.
Thank you!
> >>Then here it is.
> >
> >One thing I forgot to mention is, not surprisingly, I will also resign
> >from the committer role on the next-virtio tree.
>
> I propose myself for the committer role, I have already some experience as
> Kernel maintainer for some ARM SoCs.
Thank you again for volunteering youself to take care of it. I think
you have proved that well since you joined DPDK community :)
So Acked-by: Yuanhan Liu <yliu@fridaylinux.org>
Also Cc'ed the teckboard, per ask from Thomas.
--yliu
>
> Cheers,
> Maxime
>
> > --yliu
> >>
> >>Signed-off-by: Yuanhan Liu <yliu@fridaylinux.org>
> >>---
> >> MAINTAINERS | 3 ---
> >> 1 file changed, 3 deletions(-)
> >>
> >>diff --git a/MAINTAINERS b/MAINTAINERS
> >>index 4f1f33b..f12d83d 100644
> >>--- a/MAINTAINERS
> >>+++ b/MAINTAINERS
> >>@@ -557,7 +557,6 @@ F: doc/guides/nics/vmxnet3.rst
> >> F: doc/guides/nics/features/vmxnet3.ini
> >> Vhost-user
> >>-M: Yuanhan Liu <yliu@fridaylinux.org>
> >> M: Maxime Coquelin <maxime.coquelin@redhat.com>
> >> T: git://dpdk.org/next/dpdk-next-virtio
> >> F: lib/librte_vhost/
> >>@@ -569,14 +568,12 @@ F: doc/guides/sample_app_ug/vhost_scsi.rst
> >> Vhost PMD
> >> M: Tetsuya Mukawa <mtetsuyah@gmail.com>
> >>-M: Yuanhan Liu <yliu@fridaylinux.org>
> >> M: Maxime Coquelin <maxime.coquelin@redhat.com>
> >> T: git://dpdk.org/next/dpdk-next-virtio
> >> F: drivers/net/vhost/
> >> F: doc/guides/nics/features/vhost.ini
> >> Virtio PMD
> >>-M: Yuanhan Liu <yliu@fridaylinux.org>
> >> M: Maxime Coquelin <maxime.coquelin@redhat.com>
> >> M: Tiwei Bie <tiwei.bie@intel.com>
> >> T: git://dpdk.org/next/dpdk-next-virtio
> >>--
> >>2.7.4
next prev parent reply other threads:[~2018-02-12 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 8:51 Yuanhan Liu
2018-02-12 9:44 ` Yuanhan Liu
2018-02-12 9:54 ` Maxime Coquelin
2018-02-12 11:40 ` Yuanhan Liu [this message]
2018-02-12 13:37 ` Tan, Jianfeng
2018-03-21 21:54 ` Thomas Monjalon
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=20180212114051.GB2156@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.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).