Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp373453imu; Fri, 16 Nov 2018 04:02:08 -0800 (PST) X-Google-Smtp-Source: AJdET5dw26B97Ot0nQKgDnnu2/9NVlOomAE9+GuxvhWOD5FFW1n1JqT2dUT7NJgJ8n9NYCaAo3lF X-Received: by 2002:a17:902:4623:: with SMTP id o32-v6mr10474956pld.187.1542369728656; Fri, 16 Nov 2018 04:02:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542369728; cv=none; d=google.com; s=arc-20160816; b=jXseKY/dm7mDKX//pJAVmtIFPTE5iZyVXvDvmWVqQnIrveEnIyvLaYmkww6hQ8NilF pxYq9zrgBILDHuGuGHQ4BYDNEfpFgfhAlqmN80ZKF8hGCEDVAjhHWWyM1+MD/7mZxEZF bPClfOmpvuyoTu2fzG1yDfdyrXgh8m/PouCD1fiKHHidj3ANQb7M0qED1kyiofpgIu8A jNbO4/SimIgulivAKjH5T6f/O8vizd05lXnULo+lbnf/mq3XQ/NRKdsapkLenWl4eWNQ tOIbMqSkVFO4404xUhk/MAoWCAgmZhZlzFjYq0exKg9rCb0bqk7xYMvPvj8J02rp3/mQ ev+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=k2b9xVm87eCjSlEB+ns+tAQc3apRu5JouOkiwpRGjvk=; b=zMndvKteqwGArRWhAt4tVxhE3NQUrdPaS+gMNjzh28YsZgPRSB7zJLlvWJ0KfGmqpH NeBbKZUdBqqBMmhB/11lHZW7azFDFa1fDm+wsTuZNHGbLCaJWYwdqVnPYEEDMNuYzQqZ aMwdNLs70cr2QABMzo7zop5Mavjql1MXUIWxB/7gM9Pb1VZnSeXpn7PumXgjAYG3iWZt pLspgB+bcUzQRIGZOXK/LjYtY37jcvGN5U0mlwQ9Woi0TqndNSRQpSGXuNQROst/vlpw g3EY0H64XLE8CqSwMvi8wRDC3ZCkJPx25QjQwSUkBejaSd4A5pZLssdhMV9Ar30CwKPG qYNA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f81si16068278pfh.33.2018.11.16.04.01.52; Fri, 16 Nov 2018 04:02:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389624AbeKPWNA (ORCPT + 99 others); Fri, 16 Nov 2018 17:13:00 -0500 Received: from mx2.suse.de ([195.135.220.15]:44550 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727727AbeKPWM7 (ORCPT ); Fri, 16 Nov 2018 17:12:59 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id EC4D9AF43; Fri, 16 Nov 2018 12:00:53 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id 23A001E09B3; Fri, 16 Nov 2018 13:00:53 +0100 (CET) Date: Fri, 16 Nov 2018 13:00:53 +0100 From: Jan Kara To: Mauro Carvalho Chehab Cc: Leon Romanovsky , Dave Jiang , ksummit-discuss@lists.linuxfoundation.org, "linux-nvdimm@lists.01.org" , vishal.l.verma@intel.com, Linux Kernel Mailing List , zwisler@kernel.org Subject: Re: [Ksummit-discuss] [RFC PATCH 3/3] libnvdimm, MAINTAINERS: Subsystem Profile Message-ID: <20181116120053.GD24157@quack2.suse.cz> References: <154225759358.2499188.15268218778137905050.stgit@dwillia2-desk3.amr.corp.intel.com> <154225761038.2499188.1270468803677883744.stgit@dwillia2-desk3.amr.corp.intel.com> <20181115061036.1575223d@silica.lan> <20181115162008.GO3759@mtr-leonro.mtl.com> <20181115110919.46978343@silica.lan> <20181115193520.GA24359@mtr-leonro.mtl.com> <20181116033258.23992cde@silica.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181116033258.23992cde@silica.lan> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 16-11-18 03:33:17, Mauro Carvalho Chehab wrote: > Em Thu, 15 Nov 2018 21:35:20 +0200 > Leon Romanovsky escreveu: > > > On Thu, Nov 15, 2018 at 11:09:34AM -0800, Mauro Carvalho Chehab wrote: > > > Em Thu, 15 Nov 2018 18:20:08 +0200 > > > Leon Romanovsky escreveu: > > > > > > > On Thu, Nov 15, 2018 at 06:10:36AM -0800, Mauro Carvalho Chehab wrote: > > > > > Em Thu, 15 Nov 2018 09:03:11 +0100 > > > > > Geert Uytterhoeven escreveu: > > > > > > > > > > > Hi Dan, > > > > > > > > > > > > On Thu, Nov 15, 2018 at 6:06 AM Dan Williams wrote: > > > > > > > Document the basic policies of the libnvdimm subsystem and provide a > > > > > > > first example of a Subsystem Profile for others to duplicate and edit. > > > > > > > > > > > > > > Cc: Ross Zwisler > > > > > > > Cc: Vishal Verma > > > > > > > Cc: Dave Jiang > > > > > > > Signed-off-by: Dan Williams > > > > > > > > > > > > Thanks for your patch! > > > > > > > > > > > > > --- /dev/null > > > > > > > +++ b/Documentation/nvdimm/subsystem-profile.rst > > > > > > > > > > > > > +Trusted Reviewers > > > > > > > +----------------- > > > > > > > +Johannes Thumshirn > > > > > > > +Toshi Kani > > > > > > > +Jeff Moyer > > > > > > > +Robert Elliott > > > > > > > > > > > > Don't you want to add email addresses? > > > > > > Only the first one is listed in MAINTAINERS. > > > > > > > > > > IMO, it makes sense to have their e-mails here, in a way that it could > > > > > easily be parsed by get_maintainers.pl. > > > > > > > > I personally think that list of "trusted reviewers" makes more harm than > > > > good. It creates unneeded negative feelings to those who wanted to be in > > > > this list, but for any reason they don't. Those reviewers will feel > > > > "untrusted". > > > > > > Yeah, perhaps something like "most active reviewers" would sound > > > better. > > > > I would recommend to remove this section at all. > > New maintainers won't come out of blue, but will be come > > from existing community and such individuals for sure will see > > and judge by themselves to whom they trust and to whom not. > > I see your point, but, on the other hand, having a list with the ones > that are actively doing reviews helps newcomers. How exactly? Do you expect people to CC patches to these directly? And if yes, why is not picking patches from the mailing list good enough? Honza -- Jan Kara SUSE Labs, CR