From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965634AbdLRRqX (ORCPT ); Mon, 18 Dec 2017 12:46:23 -0500 Received: from mail-wr0-f195.google.com ([209.85.128.195]:34599 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S937564AbdLRRqP (ORCPT ); Mon, 18 Dec 2017 12:46:15 -0500 X-Google-Smtp-Source: ACJfBovFR33SVu3A85HbWVSbfgq7lquC1C4IirK9wMKzQnKxuzt+EprDRH0aTmWeBFXES92x5pWPUg== Date: Mon, 18 Dec 2017 10:46:04 -0700 From: Jason Gunthorpe To: Joe Perches Cc: Knut Omang , Stephen Hemminger , linux-kernel@vger.kernel.org, Mauro Carvalho Chehab , Nicolas Palix , Jonathan Corbet , Santosh Shilimkar , Matthew Wilcox , cocci@systeme.lip6.fr, rds-devel@oss.oracle.com, linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org, Doug Ledford , =?utf-8?Q?Micka=C3=ABl_Sala=C3=BCn?= , Shuah Khan , linux-kbuild@vger.kernel.org, Michal Marek , Julia Lawall , John Haxby , =?utf-8?Q?=C3=85smund_=C3=98stvold?= , Masahiro Yamada , Kees Cook , netdev@vger.kernel.org, Gilles Muller , "David S. Miller" , "Paul E. McKenney" , =?utf-8?B?SMOla29u?= Bugge , Andy Whitcroft , "Levin, Alexander (Sasha Levin)" Subject: Re: [PATCH v2 0/5] Support for generalized use of make C={1,2} via a wrapper program Message-ID: <20171218174604.GA19056@ziepe.ca> References: <20171216094745.5e41ac51@xeon-e3> <1513476850.31439.108.camel@oracle.com> <20171218050043.GA1307@ziepe.ca> <1513576817.31581.58.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1513576817.31581.58.camel@perches.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 17, 2017 at 10:00:17PM -0800, Joe Perches wrote: > > Today when we run checkers we get so many warnings it is too hard to > > make any sense of it. > > Here is a list of the checkpatch messages for drivers/infiniband > sorted by type. > > Many of these might be corrected by using > > $ ./scripts/checkpatch.pl -f --fix-inplace --types= \ > $(git ls-files drivers/infiniband/) How many of these do you think it is worth to fix? We do get a steady trickle of changes in this topic every cycle. Is it better to just do a big number of them all at once? Do you have an idea how disruptive this kind of work is to the whole patch flow eg new patches no longer applying to for-next, backports no longer applying, merge conflicts? Jason