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 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21E0EC4CEC5 for ; Fri, 13 Sep 2019 16:42:35 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id F3515206BB for ; Fri, 13 Sep 2019 16:42:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F3515206BB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=perches.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvdimm-bounces@lists.01.org Received: from [127.0.0.1] (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id F0637202EA3F5; Fri, 13 Sep 2019 09:42:27 -0700 (PDT) Received-SPF: None (no SPF record) identity=mailfrom; client-ip=216.40.44.54; helo=smtprelay.hostedemail.com; envelope-from=joe@perches.com; receiver=linux-nvdimm@lists.01.org Received: from smtprelay.hostedemail.com (smtprelay0054.hostedemail.com [216.40.44.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id A9A73202E843D for ; Fri, 13 Sep 2019 09:42:26 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay01.hostedemail.com (Postfix) with ESMTP id 641DF100E86C3; Fri, 13 Sep 2019 16:42:30 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: work92_8a11f0cf4e453 X-Filterd-Recvd-Size: 3136 Received: from XPS-9350.home (unknown [47.151.152.152]) (Authenticated sender: joe@perches.com) by omf01.hostedemail.com (Postfix) with ESMTPA; Fri, 13 Sep 2019 16:42:28 +0000 (UTC) Message-ID: Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS: Maintainer Entry Profile From: Joe Perches To: Rob Herring , Randy Dunlap Date: Fri, 13 Sep 2019 09:42:27 -0700 In-Reply-To: References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com> <20190911184332.GL20699@kadam> <9132e214-9b57-07dc-7ee2-f6bc52e960c5@kernel.dk> <20190913010937.7fc20d93@lwn.net> <20190913114849.GP20699@kadam> User-Agent: Evolution 3.32.1-2 MIME-Version: 1.0 X-BeenThere: linux-nvdimm@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Linux-nvdimm developer list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: ksummit , linux-nvdimm , "linux-kernel@vger.kernel.org" , bpf@vger.kernel.org, Dan Carpenter Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" On Fri, 2019-09-13 at 16:46 +0100, Rob Herring wrote: > On Fri, Sep 13, 2019 at 4:00 PM Randy Dunlap wrote: > > On 9/13/19 4:48 AM, Dan Carpenter wrote: > > > > > > So I'm expecting to take this kind of stuff into Documentation/. My own > > > > personal hope is that it can maybe serve to shame some of these "local > > > > quirks" out of existence. The evidence from this brief discussion suggests > > > > that this might indeed happen. > > > > > > I don't think it's shaming, I think it's validating. Everyone just > > > insists that since it's written in the Book of Rules then it's our fault > > > for not reading it. It's like those EULA things where there is more > > > text than anyone can physically read in a life time. > > > > Yes, agreed. > > > > > And the documentation doesn't help. For example, I knew people's rules > > > about capitalizing the subject but I'd just forget. I say that if you > > > can't be bothered to add it to checkpatch then it means you don't really > > > care that strongly. > > > > If a subsystem requires a certain spelling/capitalization in patch email > > subjects, it should be added to MAINTAINERS IMO. E.g., > > E: NuBus > > +1 > > Better make this a regex to deal with (net|net-next). > > We could probably script populating MAINTAINERS with this using how it > is done manually: git log --oneline I made a similar proposal nearly a decade ago to add a grammar to MAINTAINERS sections for patch subject prefixes. https://lore.kernel.org/lkml/1289919077.28741.50.camel@Joe-Laptop/ _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm