From: "Chen, Conghui" <conghui.chen@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, "Deng, Jie" <jie.deng@intel.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wsa@kernel.org" <wsa@kernel.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"jiedeng@alumni.sjtu.edu.cn" <jiedeng@alumni.sjtu.edu.cn>,
"vincent.whitchurch@axis.com" <vincent.whitchurch@axis.com>
Subject: RE: [PATCH] i2c: virtio: update the maintainer to Conghui
Date: Wed, 3 Nov 2021 06:15:57 +0000 [thread overview]
Message-ID: <MWHPR11MB0030EA63DDB200974685ADD0908C9@MWHPR11MB0030.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211101040814-mutt-send-email-mst@kernel.org>
Thanks for Jie's introduction, I'm very happy to have such chance to take the responsibility.
>On Mon, Nov 01, 2021 at 01:24:50PM +0800, Jie Deng wrote:
>> Due to changes in my work, I'm passing the virtio-i2c driver
>> maintenance to Conghui.
>>
>> Signed-off-by: Jie Deng <jie.deng@intel.com>
>
>Seeing as Conghui co-developed the driver, seems reasonable.
>
>Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 3b79fd4..8c9a677 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -19944,7 +19944,7 @@ F: include/uapi/linux/virtio_snd.h
>> F: sound/virtio/*
>>
>> VIRTIO I2C DRIVER
>> -M: Jie Deng <jie.deng@intel.com>
>> +M: Conghui Chen <conghui.chen@intel.com>
>> M: Viresh Kumar <viresh.kumar@linaro.org>
>> L: linux-i2c@vger.kernel.org
>> L: virtualization@lists.linux-foundation.org
>> --
>> 2.7.4
next prev parent reply other threads:[~2021-11-03 6:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 5:24 [PATCH] i2c: virtio: update the maintainer to Conghui Jie Deng
2021-11-01 8:08 ` Michael S. Tsirkin
2021-11-03 6:15 ` Chen, Conghui [this message]
2021-11-02 3:33 ` Viresh Kumar
2021-11-05 21:54 ` Wolfram Sang
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=MWHPR11MB0030EA63DDB200974685ADD0908C9@MWHPR11MB0030.namprd11.prod.outlook.com \
--to=conghui.chen@intel.com \
--cc=jie.deng@intel.com \
--cc=jiedeng@alumni.sjtu.edu.cn \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=vincent.whitchurch@axis.com \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).