From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, mingo@elte.hu
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, trivial@kernel.org
Subject: [PATCH 0/5] x86: coding style fixes in arch/x86/ia32/
Date: Tue, 8 Jan 2008 20:31:38 +0100 [thread overview]
Message-ID: <20080108203138.4d43937c@paolo-desktop> (raw)
Hi all,
the following 5 patches fix 227 errors and 2 warnings
reported by checkpatch.pl
I hope they don't introduce problems in the process and
that they can be applied.
I know there is no agreement on the list about whether these
patches should be posted/accepted or not so I'm just resending
the mangled patches that already hit the list.
I'll then start working what Andi suggested here:
http://lkml.org/lkml/2008/1/8/213
Ingo, I would appreciated your feedback about the work I'm
doing, if you want me to stop or continue.
If you want me to work on further fixes I would appreciate
if you could indicate files that needs fixing minimazing
impacts on the overall process.
Thanks.
--- BEFORE ---
ia32_signal.c
total: 96 errors, 11 warnings, 617 lines checked
ia32_binfmt.c
total: 41 errors, 5 warnings, 285 lines checked
ia32_aout.c
total: 50 errors, 18 warnings, 528 lines checked
fpu32.c
total: 39 errors, 1 warnings, 183 lines checked
audit.c
total: 1 errors, 0 warnings, 42 lines checked
Total
total: 227 errors, 35 warnings
--- AFTER ---
ia32_signal.c
total: 3 errors, 9 warnings, 617 lines checked
ia32_binfmt.c
total: 2 errors, 5 warnings, 285 lines checked
ia32_aout.c
total: 2 errors, 18 warnings, 526 lines checked
fpu32.c
total: 2 errors, 1 warnings, 183 lines checked
audit.c
total: 0 errors, 0 warnings, 42 lines checked
Total
total: 9 errors, 33 warning
--
Paolo
paolo.ciarrocchi.googlepages.com
next reply other threads:[~2008-01-08 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 19:31 Paolo Ciarrocchi [this message]
2008-01-08 21:38 ` [PATCH 0/5] x86: coding style fixes in arch/x86/ia32/ Ingo Molnar
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=20080108203138.4d43937c@paolo-desktop \
--to=paolo.ciarrocchi@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=trivial@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