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: <20221214063107.fazrfq3n26hw4ndl@vireshk-i7>
Date:   Wed, 14 Dec 2022 12:01:07 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     wsa@...nel.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

On 14-12-22, 13:36, Conghui wrote:
> This updates the maintainer for virtio i2c drvier
> 
> Signed-off-by: Conghui <conghui.chen@...el.com>
> Acked-by: Jian Jun Chen <jian.jun.chen@...el.com>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a8c8f6b42436..44747f4641a6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -21920,7 +21920,7 @@ F:	include/uapi/linux/virtio_snd.h
>  F:	sound/virtio/*
>  
>  VIRTIO I2C DRIVER
> -M:	Conghui Chen <conghui.chen@...el.com>
> +M:	Jian Jun Chen <jian.jun.chen@...el.com>
>  M:	Viresh Kumar <viresh.kumar@...aro.org>
>  L:	linux-i2c@...r.kernel.org
>  L:	virtualization@...ts.linux-foundation.org

Wolfram,

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 ?

-- 
viresh