linux-kernel - Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 27 Dec 2022 02:21:59 -0500
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     "Chen, Jian Jun" <jian.jun.chen@...el.com>
Cc:     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
Subject: Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c

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
> > > 
> >