Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp801267rwb; Wed, 14 Dec 2022 03:01:46 -0800 (PST) X-Google-Smtp-Source: AA0mqf4s7m9gckjDdot7xmGqQtjpjPiaMBRvNMogkj1kOjDwajRK7ZVooNnsEp2+EeioZ4VbVK7R X-Received: by 2002:aa7:9289:0:b0:56c:318a:f83b with SMTP id j9-20020aa79289000000b0056c318af83bmr24731616pfa.13.1671015705893; Wed, 14 Dec 2022 03:01:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671015705; cv=none; d=google.com; s=arc-20160816; b=0ZGbngKc4kla63qKSMFm4Oqx44l1be8rWNlDYIkZgU0T63+pqnVtfwzUk2ZR6LxDd6 GFLGR0pfWHgzv5Z+iHjBvcC8UWGvoBoglhpeN61UMEF2M/3fopL8Mt8eC776ardHhW9K 5GEss4sAf9dqDpWQfRWiC49plSA77BtWp78l9Shg3hIdeReqLUSMN3c5iAxmSWC0Buba um5wocOhO+ROxPq0js0xnkIkHTBqIT2g97tmS1ftCNDFsN4lfsfw4tadxM4/LO+GFDYG lmX5ofepAPamKP997WdiHI2NRixyn21+G76H+UyH4rmrV8TPzaVFUTNL2/ZicRrlTaJ9 dxEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:to:from:date:dkim-signature; bh=++Gb2lBFkve8gSRO08jWImahxW9f7wYHqGKRXd6CCqk=; b=siahKBiTWsxn5781Mfs/bfMzLrHnfvC/lqBmDfhZRjwnWbQ/eVusMD/LQnJ/Tzd70I Vjn/4OhHSML46tSGSnVATi9Q4ZqWFkjagVKYzPGq/ZngLDb6Sm1HTywiHX4czFIF0T/3 X1puTF3xhbcnixXC9WttTTX5UnFS8hoJkH8CyZpwUdHKxzNrurg7zlfWHes8TsBpbd5A 13hNNbLQn2/JJZTe8aeLvapa27noGEF/vd8n34VQau0B4lQRxnqvFq/u5929WS96VGHb xtU9rfBHyEtXgEY1bstOAEx2nVVteBp3lYaSZ9FhhyNQfABnEVIA3wXx/WmKMMLXkIT5 P5tA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ZuHbhCVH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 12-20020a62140c000000b00571d38602bcsi14111381pfu.295.2022.12.14.03.01.30; Wed, 14 Dec 2022 03:01:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=ZuHbhCVH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237909AbiLNK4t (ORCPT + 70 others); Wed, 14 Dec 2022 05:56:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58218 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237557AbiLNK4q (ORCPT ); Wed, 14 Dec 2022 05:56:46 -0500 Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3FD316343 for ; Wed, 14 Dec 2022 02:56:46 -0800 (PST) Received: by mail-pj1-x102e.google.com with SMTP id o1-20020a17090a678100b00219cf69e5f0so6755985pjj.2 for ; Wed, 14 Dec 2022 02:56:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=++Gb2lBFkve8gSRO08jWImahxW9f7wYHqGKRXd6CCqk=; b=ZuHbhCVHQ5/Vbs7yHy20WY/2sODWYzCNxqrrUnPubbka9QwUiFyRa5t8+3IPkBYYn3 6cU6EiIT/p7UoDbDYuw1+r7PXsDGq5eJeAXOsx/6e0StGgxj9xZ+9F1TuyRHkkkdUX0C m/HlkmP68kTOLdp64++soEzCWGFZ26LYRVWCd/UYlYmdfU7c+2lb0YjKC8VBQ0mVWCZM s0IHFJgxDRXU7bDCV13nK+I4Kru/sdZep1qCGtmsXOIj0hpMYrAZzo/MmoxNUN/+W1cE 7kPReEeqtU53/7zapaXILjNjwWBbzyoc7OFg4JaOPnAX8NqB8kCimdqYsYn/b5PuNjNL XwmQ== 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=++Gb2lBFkve8gSRO08jWImahxW9f7wYHqGKRXd6CCqk=; b=HyVQ8HtrPqWMH7lbMguJQXO42NYwm3C+z1gEiRnJDXOi7q6D8fkzk0nn2r0DjLm/ce 78kj48HhXZEtdqbG/ycow3i8zrntMfznu2spMpplVhGSSKtAbw68PyCXy1ASoO8waheL IhqBx0v26N0ZyZD8Zixp/4nW4O+WJiBfd+1tZy69Rg8xzC/4mBWTFGRLgfeINXziTvoO 8xfVq3aUt6KrgcgYAPE70Gj4crlw9yQqd7iUYS6uUS7dBS1Erj9HU4XSBhu99KnVwNM+ 5RIaB641aLMLpxGAL620QN7bIENo6L8/OZj+tc2Q6byBvpxU0SxIsUsFyh0AXodw0oVE N1Cw== X-Gm-Message-State: ANoB5plj5ND2Kn37XMNdVLfvTpNhiHenhn2My/kDS6SPeuESujwZYbJr kVs4ESjwCDaSD+yYYsNxEnssIg== X-Received: by 2002:a17:902:f64b:b0:186:de2c:97e3 with SMTP id m11-20020a170902f64b00b00186de2c97e3mr23744609plg.54.1671015405704; Wed, 14 Dec 2022 02:56:45 -0800 (PST) Received: from localhost ([122.172.87.149]) by smtp.gmail.com with ESMTPSA id d22-20020a63fd16000000b00439c6a4e1ccsm8163703pgh.62.2022.12.14.02.56.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Dec 2022 02:56:44 -0800 (PST) Date: Wed, 14 Dec 2022 16:26:42 +0530 From: Viresh Kumar To: Wolfram Sang , mst@redhat.com, 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: <20221214105642.3xagckvbbgu5mubl@vireshk-i7> 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: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14-12-22, 11:20, Wolfram Sang wrote: > 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. Sure, a stale entry is always bad. > 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? It was a general question that I asked myself and didn't know an answer to. I wasn't sure if adding someone to be a maintainer here to a driver, which they haven't contributed to until now (at least based on open source commits), is right or not, since this isn't a stale entry in MAINTAINERS anyway. An entry as R: would be okay normally IMO, as this makes sure interested party is kept aware of the development in the area. An M: entry somehow gives a higher level of authority to the person and without any prior contributions, it feels tricky at least. Anyway, I don't have any objection to the patch at least as it was primarily developed by Intel engineers. Acked-by: Viresh Kumar -- viresh