From: Ingo Molnar <mingo@elte.hu>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: hpa <hpa@zytor.com>, Linux Kernel <linux-kernel@vger.kernel.org>,
tglx <tglx@linutronix.de>
Subject: Re: [PATCH 2/5] x86: Coding style fixes to arch/x86/kernel/bios_uv.c
Date: Fri, 15 Aug 2008 16:52:57 +0200 [thread overview]
Message-ID: <20080815145257.GL12954@elte.hu> (raw)
In-Reply-To: <20080802212406.047e8ae6@paolo-desktop>
* Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> Before:
> total: 5 errors, 0 warnings, 48 lines checked
>
> After:
> total: 0 errors, 0 warnings, 58 lines checked
>
> paolo@paolo-desktop:~/linux.trees.git$ md5sum /tmp/bios_uv.o.*
> 9afe794594831166704744184e192ed8 /tmp/bios_uv.o.after
> 9afe794594831166704744184e192ed8 /tmp/bios_uv.o.before
>
> Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> ---
> arch/x86/kernel/bios_uv.c | 20 +++++++++++++++-----
> 1 files changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/kernel/bios_uv.c b/arch/x86/kernel/bios_uv.c
> index c639bd5..100e759 100644
> --- a/arch/x86/kernel/bios_uv.c
> +++ b/arch/x86/kernel/bios_uv.c
> @@ -25,11 +25,21 @@ x86_bios_strerror(long status)
> {
> const char *str;
> switch (status) {
> - case 0: str = "Call completed without error"; break;
> - case -1: str = "Not implemented"; break;
> - case -2: str = "Invalid argument"; break;
> - case -3: str = "Call completed with error"; break;
> - default: str = "Unknown BIOS status code"; break;
> + case 0:
> + str = "Call completed without error";
> + break;
> + case -1:
> + str = "Not implemented";
> + break;
> + case -2:
> + str = "Invalid argument";
> + break;
> + case -3:
> + str = "Call completed with error";
> + break;
> + default:
> + str = "Unknown BIOS status code";
> + break;
hm - i changed your patch to the one below, to align the break's
vertically, which makes the original variant a lot more readable (and
even more readable than the new one). Checkpatch still complains about
it but that's OK, there are always exceptions.
Ingo
------------------->
Subject: x86: coding style fixes to arch/x86/kernel/bios_uv.c
From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date: Sat, 2 Aug 2008 21:24:06 +0200
paolo@paolo-desktop:~/linux.trees.git$ md5sum /tmp/bios_uv.o.*
9afe794594831166704744184e192ed8 /tmp/bios_uv.o.after
9afe794594831166704744184e192ed8 /tmp/bios_uv.o.before
Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/bios_uv.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
Index: tip/arch/x86/kernel/bios_uv.c
===================================================================
--- tip.orig/arch/x86/kernel/bios_uv.c
+++ tip/arch/x86/kernel/bios_uv.c
@@ -25,11 +25,11 @@ x86_bios_strerror(long status)
{
const char *str;
switch (status) {
- case 0: str = "Call completed without error"; break;
- case -1: str = "Not implemented"; break;
- case -2: str = "Invalid argument"; break;
- case -3: str = "Call completed with error"; break;
- default: str = "Unknown BIOS status code"; break;
+ case 0: str = "Call completed without error"; break;
+ case -1: str = "Not implemented"; break;
+ case -2: str = "Invalid argument"; break;
+ case -3: str = "Call completed with error"; break;
+ default: str = "Unknown BIOS status code"; break;
}
return str;
}
next prev parent reply other threads:[~2008-08-15 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 19:24 [PATCH 2/5] x86: Coding style fixes to arch/x86/kernel/bios_uv.c Paolo Ciarrocchi
2008-08-03 4:01 ` H. Peter Anvin
2008-08-03 10:51 ` Stefan Richter
2008-08-03 11:54 ` Krzysztof Halasa
2008-08-03 12:21 ` Paolo Ciarrocchi
2008-08-05 2:15 ` H. Peter Anvin
2008-08-15 14:52 ` Ingo Molnar [this message]
2008-08-16 10:30 ` Paolo Ciarrocchi
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=20080815145257.GL12954@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=tglx@linutronix.de \
/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