From: Joe Perches <joe@perches.com>
To: Bogicevic Sasa <brutallesale@gmail.com>, bhelgaas@google.com
Cc: 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
Subject: Re: [PATCH] drivers:pci Fix all whitespace issues
Date: Sun, 27 Dec 2015 09:21:34 -0800 [thread overview]
Message-ID: <1451236894.1098.5.camel@perches.com> (raw)
In-Reply-To: <1451234408-42250-1-git-send-email-brutallesale@gmail.com>
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.
next prev parent reply other threads:[~2015-12-27 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 16:40 [PATCH] drivers:pci Fix all whitespace issues Bogicevic Sasa
2015-12-27 17:21 ` Joe Perches [this message]
2015-12-27 17:56 ` sasa bogicevic
-- strict thread matches above, loose matches on Subject: below --
2015-12-27 21:21 Bogicevic Sasa
2016-01-08 16:36 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1451236894.1098.5.camel@perches.com \
--to=joe@perches.com \
--cc=Richard.Zhu@freescale.com \
--cc=bhelgaas@google.com \
--cc=brutallesale@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox