From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752932AbcLLTls (ORCPT ); Mon, 12 Dec 2016 14:41:48 -0500 Received: from casper.infradead.org ([85.118.1.10]:50274 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbcLLTlr (ORCPT ); Mon, 12 Dec 2016 14:41:47 -0500 Date: Mon, 12 Dec 2016 19:41:41 +0000 (GMT) From: James Simmons To: Joe Perches cc: Greg Kroah-Hartman , Ben Evans , "devel@driverdev.osuosl.org" , Andreas Dilger , Oleg Drokin , Linux Kernel Mailing List , Lustre Development List Subject: Re: [PATCH v2 3/5] staging: lustre: headers: sort headers affected by obdo move In-Reply-To: <1481566746.1764.26.camel@perches.com> Message-ID: References: <1481393161-22623-1-git-send-email-jsimmons@infradead.org> <1481393161-22623-4-git-send-email-jsimmons@infradead.org> <20161210181433.GA8477@kroah.com> <20161212163455.GA21011@kroah.com> <1481566746.1764.26.camel@perches.com> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20161212_194141_332304_89C7E264 X-CRM114-Status: GOOD ( 16.26 ) X-Spam-Score: -1.9 (-) X-Spam-Report: SpamAssassin version 3.4.1 on casper.infradead.org summary: Content analysis details: (-1.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 NO_RELAYS Informational: message was not relayed via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Mon, 2016-12-12 at 17:34 +0100, Greg Kroah-Hartman wrote: > > A: Top-posting. > > Q: What is the most annoying thing in e-mail? > > > > A: No. > > Q: Should I include quotations after my reply? > > > > http://daringfireball.net/2007/07/on_top > > > > On Mon, Dec 12, 2016 at 02:42:29PM +0000, Ben Evans wrote: > > > This was done to conform to the Lustre Coding Guidelines. > > > > What is this mythical guidelines, and why does it differ from the kernel > > source ones? > > It's not like it's hard to find > http://wiki.lustre.org/Lustre_Coding_Style_Guidelines > > And in specific: > http://wiki.lustre.org/Lustre_Style_Guide_Includes > > There is no single mandated code style for this. > Some people like reverse christmas tree. > > Whatever... > Sigh, Sayre's law. I went looking to see what the offical policy is for this and found nothing. If this is really important can we then place an offical policy on how headers are added to a C file in CodingStyle and add something to checkpatch to detect incorrect patches. Lets burn down this bike shed once and for all.