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,URIBL_BLOCKED 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 91C10C4CEC7 for ; Thu, 12 Sep 2019 23:07:59 +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 6131220856 for ; Thu, 12 Sep 2019 23:07:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6131220856 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 214DB202E6E17; Thu, 12 Sep 2019 16:07:58 -0700 (PDT) Received-SPF: None (no SPF record) identity=mailfrom; client-ip=216.40.44.30; helo=smtprelay.hostedemail.com; envelope-from=joe@perches.com; receiver=linux-nvdimm@lists.01.org Received: from smtprelay.hostedemail.com (smtprelay0030.hostedemail.com [216.40.44.30]) (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 DBC56202E6E0E for ; Thu, 12 Sep 2019 16:07:56 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id B5AD9837F24A; Thu, 12 Sep 2019 23:07:56 +0000 (UTC) X-Session-Marker: 6A6F6540706572636865732E636F6D X-HE-Tag: thumb06_624660a277f15 X-Filterd-Recvd-Size: 1827 Received: from XPS-9350.home (unknown [47.151.152.152]) (Authenticated sender: joe@perches.com) by omf12.hostedemail.com (Postfix) with ESMTPA; Thu, 12 Sep 2019 23:07:55 +0000 (UTC) Message-ID: Subject: Re: [PATCH 00/13] nvdimm: Use more common kernel coding style From: Joe Perches To: Nick Desaulniers Date: Thu, 12 Sep 2019 16:07:53 -0700 In-Reply-To: References: <4df0a07ec8f1391acfa987ecef184a50e7831000.camel@perches.com> <4f759f8c4f4d59fd60008e833334e29b0da0869c.camel@perches.com> 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: linux-nvdimm , linux-kernel , Miguel Ojeda , 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 Thu, 2019-09-12 at 16:00 -0700, Nick Desaulniers wrote: > Consider the fact that not all kernel developers run checkpatch.pl. > Is that a deficiency in checkpatch.pl, or the lack of enforcement in > kernel developers' workflows? No. Mostly it's because the kernel is like a bunch of little untethered development planets, each with a little prince that wants to keep their own little fiefdom separate from the others. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm