[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221214065856-mutt-send-email-mst@kernel.org>
Date: Wed, 14 Dec 2022 07:00:00 -0500
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Wolfram Sang <wsa@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>, asowang@...hat.com,
Conghui <conghui.chen@...el.com>, linux-i2c@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org,
Jian Jun Chen <jian.jun.chen@...el.com>
Subject: Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c
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.
> If not, then not. We can fix this, too, if
> needed.
>
> What is the reason for your question?
>
> All the best,
>
> Wolfram
>
Powered by blists - more mailing lists