From: Ingo Molnar <mingo@kernel.org>
To: Valentina Manea <valentina.manea.m@gmail.com>
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, bhelgaas@google.com, gregkh@linuxfoundation.org,
bin.gao@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/pci: fix checkpatch.pl indentation warnings
Date: Fri, 12 Jul 2013 12:26:41 +0200 [thread overview]
Message-ID: <20130712102641.GA13675@gmail.com> (raw)
In-Reply-To: <1373523787-8249-1-git-send-email-valentina.manea.m@gmail.com>
* Valentina Manea <valentina.manea.m@gmail.com> wrote:
> This patch fixes warnings generated by checkpatch.pl
> regarding indentation.
>
> Signed-off-by: Valentina Manea <valentina.manea.m@gmail.com>
> ---
> arch/x86/pci/mrst.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/pci/mrst.c b/arch/x86/pci/mrst.c
> index 6eb18c4..cd0a373 100644
> --- a/arch/x86/pci/mrst.c
> +++ b/arch/x86/pci/mrst.c
> @@ -251,8 +251,8 @@ static void pci_d3delay_fixup(struct pci_dev *dev)
> {
> /* PCI fixups are effectively decided compile time. If we have a dual
> SoC/non-SoC kernel we don't want to mangle d3 on non SoC devices */
> - if (!pci_soc_mode)
> - return;
> + if (!pci_soc_mode)
> + return;
> /* true pci devices in lincroft should allow type 1 access, the rest
> * are langwell fake pci devices.
> */
If you do whitespace cleanups then please also fix all the other problems
in that file, right now mrst.c has more than just one:
total: 3 errors, 7 warnings, 3 checks, 303 lines checked
plus the area you patched has some wierd comment formatting as well. For
multi-line comments we use:
/*
* Comment .....
* ...... goes here.
*/
as specified in Documentation/CodingStyle.
Thanks,
Ingo
prev parent reply other threads:[~2013-07-12 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 6:23 [PATCH] x86/pci: fix checkpatch.pl indentation warnings Valentina Manea
2013-07-12 10:26 ` Ingo Molnar [this message]
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=20130712102641.GA13675@gmail.com \
--to=mingo@kernel.org \
--cc=bhelgaas@google.com \
--cc=bin.gao@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=valentina.manea.m@gmail.com \
--cc=x86@kernel.org \
/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