From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EFEB7C001B2 for ; Wed, 14 Dec 2022 12:01:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238113AbiLNMBV (ORCPT ); Wed, 14 Dec 2022 07:01:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34576 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238374AbiLNMAy (ORCPT ); Wed, 14 Dec 2022 07:00:54 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9EC561D648 for ; Wed, 14 Dec 2022 04:00:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671019205; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ORJ82nUqgmRWHPSLvhoNWLJ0+9bS/SAj60kUH3rLBhw=; b=MOSMM2kQrAq1q5srvZDDwdIkI0kfgkP3iBsd3xG0sH3INj/YYTleJaHF0vF9AYp0InRWve zZ/yuugfEnWUZ5UbXPf6/nDhbsmE6RZTb4iH/+crITKqoB24chZ0l5o+SO4OI/QyuVhKgT cdNHN58jctER5OtWQLIdPakLcTQ656M= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-338-3S6JxOJZMtqILFkVAbQZew-1; Wed, 14 Dec 2022 07:00:04 -0500 X-MC-Unique: 3S6JxOJZMtqILFkVAbQZew-1 Received: by mail-wm1-f70.google.com with SMTP id f20-20020a7bc8d4000000b003d1cda5bd6fso4084297wml.9 for ; Wed, 14 Dec 2022 04:00:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ORJ82nUqgmRWHPSLvhoNWLJ0+9bS/SAj60kUH3rLBhw=; b=jacGhNcRIbfjOWkqiP7LC657VqezhyHC6f2g+AxSyd1yWXBFpS6kp6WmdgUATQNmXz ciAOolIAi4Xn0nwqA0AQd8Q/nEBoSOj5BkwtqO9V0tBcOK20uQCUqKvH1BQX22cNOaFf dO3fxZrhGJXJmH7kkS3sWTazyvoAKvz7eC3jtG7+bkiJTI/zM3J9h/elAX7tUBbXOHR4 35rElCFtxCymAXk9BC2A0Nl/NPasjc80CVBtD/HkJf/xaQh6dsgGn5Kc5SDr11SyMZHY B9TEFj/tpCXeK5JzLUhgxYkjb66b7sd/SHPNrS5grDtmrlKg5GnziFIq3WuhetKBazXq TQ/Q== X-Gm-Message-State: ANoB5plu8/4Iv3u/avAjydmwyhoc7il8zTj8cWg+g9mHZVDuJk0xwIYT 587S2+vblivit7CZdkhxGyU78MUjucMEs3modnXJ08iUTeFkCF9Yz2q3IkI1k8l34FPBxSeJdUq U47nURfSG6pUalzSeUQ884MJF X-Received: by 2002:a5d:464d:0:b0:242:19ba:c325 with SMTP id j13-20020a5d464d000000b0024219bac325mr14267626wrs.30.1671019203248; Wed, 14 Dec 2022 04:00:03 -0800 (PST) X-Google-Smtp-Source: AA0mqf70rUn2JP0a8uV9qrEQRacU9eDMVqCZ636ZVH7ao6T+VGi+4vl1vzH82Lks4swv/K9ZhapOSw== X-Received: by 2002:a5d:464d:0:b0:242:19ba:c325 with SMTP id j13-20020a5d464d000000b0024219bac325mr14267609wrs.30.1671019202999; Wed, 14 Dec 2022 04:00:02 -0800 (PST) Received: from redhat.com (bzq-82-81-161-50.red.bezeqint.net. [82.81.161.50]) by smtp.gmail.com with ESMTPSA id l7-20020a5d6687000000b002425787c5easm2609121wru.96.2022.12.14.04.00.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Dec 2022 04:00:02 -0800 (PST) Date: Wed, 14 Dec 2022 07:00:00 -0500 From: "Michael S. Tsirkin" To: Wolfram Sang , Viresh Kumar , asowang@redhat.com, Conghui , linux-i2c@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Jian Jun Chen Subject: Re: [PATCH] MAINTAINERS: Update maintainer list for virtio i2c Message-ID: <20221214065856-mutt-send-email-mst@kernel.org> References: <20221214053631.3225164-1-conghui.chen@intel.com> <20221214063107.fazrfq3n26hw4ndl@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 >