Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753260AbbL0R4X (ORCPT ); Sun, 27 Dec 2015 12:56:23 -0500 Received: from mail-wm0-f51.google.com ([74.125.82.51]:36794 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463AbbL0R4U convert rfc822-to-8bit (ORCPT ); Sun, 27 Dec 2015 12:56:20 -0500 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: [PATCH] drivers:pci Fix all whitespace issues From: sasa bogicevic In-Reply-To: <1451236894.1098.5.camel@perches.com> Date: Sun, 27 Dec 2015 18:56:16 +0100 Cc: bhelgaas@google.com, Richard.Zhu@freescale.com, l.stach@pengutronix.de, rjw@rjwysocki.net, lenb@kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Content-Transfer-Encoding: 8BIT Message-Id: References: <1451234408-42250-1-git-send-email-brutallesale@gmail.com> <1451236894.1098.5.camel@perches.com> To: Joe Perches X-Mailer: Apple Mail (2.3112) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2085 Lines: 56 Hi Joe, No this is not done with checkpatch.pl I just used it to verify that my changes are correct. I was wondering why that “type” pointer threw errors since it looks fine to me the way it was declared. This “type*” is just present in few of the files I can just redo those changes and send the patch again. Thanks, Sasa { name: Bogicevic Sasa phone: +381606006200 } > On Dec 27, 2015, at 18:21, Joe Perches wrote: > > On Sun, 2015-12-27 at 08:40 -0800, Bogicevic Sasa wrote: >> This patch fixes all whitespace issues( missing or needed whitespace) in >> all files in drivers/pci folder. Code is compiled with allyesconfig >> before and after code changes and objects are recorded and checked with >> objdiff and they are not changed after this commit. > [] >> diff --git a/drivers/pci/access.c b/drivers/pci/access.c > [] >> @@ -25,9 +25,9 @@ DEFINE_RAW_SPINLOCK(pci_lock); >> #define PCI_word_BAD (pos & 1) >> #define PCI_dword_BAD (pos & 3) >> >> -#define PCI_OP_READ(size,type,len) \ >> +#define PCI_OP_READ(size, type, len) \ >> int pci_bus_read_config_##size \ >> - (struct pci_bus *bus, unsigned int devfn, int pos, type *value) \ >> + (struct pci_bus *bus, unsigned int devfn, int pos, type * value) \ >> { \ >> int res; \ >> unsigned long flags; \ >> @@ -40,7 +40,7 @@ int pci_bus_read_config_##size \ >> return res; \ >> } > > When the first entry I look at is improper, I wonder > about the rest. > > Was this done with checkpatch --types=spacing --fix ? > > If so, because checkpatch is brainless, you need to > visually verify each change. > > This "type" use is a macro argument indicating > what actual c90 type is being used in a function. > > The original code is nominally correct, but checkpatch > doesn't know that "type" is not a variable. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/