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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y5mjcuCRP45ynJis@shikoro>
Date:   Wed, 14 Dec 2022 11:20:34 +0100
From:   Wolfram Sang <wsa@...nel.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     mst@...hat.com, 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

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. If not, then not. We can fix this, too, if
needed.

What is the reason for your question?

All the best,

   Wolfram

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)