From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Chen, Jian Jun" <jian.jun.chen@intel.com>
Cc: asowang@redhat.com, Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, Conghui <conghui.chen@intel.com>
Subject: Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c
Date: Tue, 27 Dec 2022 02:21:59 -0500 [thread overview]
Message-ID: <20221227022149-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <fd9bc91a-8afe-9dac-7d1f-2e57e658d2d7@intel.com>
On Tue, Dec 27, 2022 at 12:05:09PM +0800, Chen, Jian Jun wrote:
>
> On 12/14/2022 20:00, Michael S. Tsirkin wrote:
> > On Wed, Dec 14, 2022 at 11:20:34AM +0100, Wolfram Sang wrote:
> > > Hi Viresh,
> > >
> > > > I understand that it is okay to pass the maintainership, within the
> > > > company, for platform specific parts from one person to another, since
> > > > they have the best knowledge of the code and are the only one
> > > > interested in maintaining it too.
> > > >
> > > > But what is the rule for generic drivers like this one ?
> > > Dunno if this is really a rule, but if a maintainer steps out and makes
> > > sure there is someone to pick up the work, this is more than welcome.
> > > Way better than a stale entry in the MAINTAINERS file.
> > >
> > > I mean, it does not limit the chance to have further maintainers, for
> > > example. I believe in meritocracy here. Those who do and collaborate,
> > > shall get responsibility.
> > Exactly. I'd like to see Jian Jun Chen do and collaborate first.
>
> Hi Michael,
>
> Sure, I will start to collaborate first.
Great!
> > > If not, then not. We can fix this, too, if
> > > needed.
> > >
> > > What is the reason for your question?
> > >
> > > All the best,
> > >
> > > Wolfram
> > >
> >
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-12-27 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221214053631.3225164-1-conghui.chen@intel.com>
2022-12-14 6:31 ` [PATCH] MAINTAINERS: Update maintainer list for virtio i2c Viresh Kumar
[not found] ` <Y5mjcuCRP45ynJis@shikoro>
2022-12-14 10:56 ` Viresh Kumar
2022-12-14 11:58 ` Michael S. Tsirkin
2022-12-14 12:00 ` Michael S. Tsirkin
2022-12-27 4:05 ` Chen, Jian Jun
2022-12-27 7:21 ` Michael S. Tsirkin [this message]
2022-12-14 11:37 ` Michael S. Tsirkin
2022-12-27 4:04 ` Chen, Jian Jun
2022-12-27 7:08 ` Michael S. Tsirkin
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=20221227022149-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=asowang@redhat.com \
--cc=conghui.chen@intel.com \
--cc=jian.jun.chen@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).