From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 13 Sep 2016 12:45:20 -0700 From: Josh Triplett To: Christian Borntraeger Message-ID: <20160913194520.GA8071@cloud> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: ksummit-discuss@lists.linux-foundation.org, Joe Perches Subject: Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Sep 13, 2016 at 08:58:49PM +0200, Christian Borntraeger wrote: > 3. CodingStyle seems to get changes which have no ACK or Reviewed-by that seem > to be controversial. e.g. > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/Documentation/CodingStyle?id=865a1caa4b6b886babdd9d67e7c3608be4567a51 > suggested to indent labels with a space, and was then immediately followed by > patches. Is there a process in place to verify and challenge such changes? Ideally, that should come up during review of the CodingStyle patch. Changes shouldn't go into CodingStyle except to document existing process and unwritten rules, or to document the results of a discussion and consensus. That particular change to CodingStyle should have been rejected, and should be reverted. - Josh Triplett