[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1528624.HcuCny6IaW@vostro.rjw.lan>
Date: Thu, 05 Mar 2015 00:04:54 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: al.stone@...aro.org
Cc: lenb@...nel.org, catalin.marinas@....com, will.deacon@....com,
robert.moore@...el.com, tony.luck@...el.com, fenghua.yu@...el.com,
linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, devel@...ica.org,
linux-arm-kernel@...ts.infradead.org, linaro-acpi@...ts.linaro.org,
linaro-kernel@...ts.linaro.org, patches@...aro.org
Subject: Re: [PATCH v3 1/9] ACPI: fix all errors reported by cleanpatch.pl in osl.c
On Tuesday, February 24, 2015 05:36:17 PM al.stone@...aro.org wrote:
> From: Al Stone <al.stone@...aro.org>
>
> In preparation for later splitting out some of the arch-dependent code from
> osl.c, clean up the errors reported by checkpatch.pl. They fell into these
> classes:
>
> -- remove the FSF address from the GPL notice
> -- "foo * bar" should be "foo *bar" (and the ** variation of same)
> -- a return is not a function, so parentheses are not required.
>
> Signed-off-by: Al Stone <al.stone@...aro.org>
checkpatch.pl is irrelevant here. You're trying to make the coding style be
more consistent with the coding style of the rest of the kernel.
The warnings from checkpatch.pl are meaningless for the existing code, so
it should not be used to justify changes in that code.
Of course, the same applies to patches [2-4/9].
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists