From: Dmitri Vorobiev <dmitri.vorobiev@movial.fi>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, hpa <hpa@zytor.com>,
tglx <tglx@linutronix.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/5] x86: Coding style fixes to arch/x86/lib/strstr_32.c
Date: Mon, 04 Aug 2008 09:20:09 +0300 [thread overview]
Message-ID: <48969F99.1060301@movial.fi> (raw)
In-Reply-To: <20080802212445.72fb1d77@paolo-desktop>
Paolo Ciarrocchi wrote:
> Before:
> total: 3 errors, 0 warnings, 31 lines checked
>
> After:
> total: 0 errors, 0 warnings, 31 lines checked
>
> paolo@paolo-desktop:~/linux.trees.git$ md5sum /tmp/strstr_32.o.*
It seems very tempting to merge this file with arch/x86/lib/string_32.c, or is there any compelling reason to keep these two separate?
> c96006ec3387862e5bacb139207a3098 /tmp/strstr_32.o.after
> c96006ec3387862e5bacb139207a3098 /tmp/strstr_32.o.before
>
> Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> ---
> arch/x86/lib/strstr_32.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/lib/strstr_32.c b/arch/x86/lib/strstr_32.c
> index 42e8a50..8e2d55f 100644
> --- a/arch/x86/lib/strstr_32.c
> +++ b/arch/x86/lib/strstr_32.c
> @@ -23,9 +23,9 @@ __asm__ __volatile__(
> "jne 1b\n\t"
> "xorl %%eax,%%eax\n\t"
> "2:"
> - :"=a" (__res), "=&c" (d0), "=&S" (d1)
> - :"0" (0), "1" (0xffffffff), "2" (cs), "g" (ct)
> - :"dx", "di");
> + : "=a" (__res), "=&c" (d0), "=&S" (d1)
> + : "0" (0), "1" (0xffffffff), "2" (cs), "g" (ct)
> + : "dx", "di");
> return __res;
It's strange that checkpatch.pl does not cater for such an obvious style violation as this last line.
Dmitri
> }
>
prev parent reply other threads:[~2008-08-04 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 19:24 [PATCH 3/5] x86: Coding style fixes to arch/x86/lib/strstr_32.c Paolo Ciarrocchi
2008-08-04 6:20 ` Dmitri Vorobiev [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=48969F99.1060301@movial.fi \
--to=dmitri.vorobiev@movial.fi \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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