From: "Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [PATCH 0/24] x86: arch/x86/kernel/ cleanups
Date: Mon, 28 Jul 2008 18:37:44 -0300 [thread overview]
Message-ID: <6b53b1990807281437l707be573n3be4d85feb033c63@mail.gmail.com> (raw)
In-Reply-To: <20080728212052.GB9986@elte.hu>
On Mon, Jul 28, 2008 at 6:20 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Gustavo F. Padovan <gustavo@las.ic.unicamp.br> wrote:
>
>> Ingo,
>>
>> I removed many extra whitespaces and tabs from arch/x86/kernel/
>
> hm, we tend to do a full cleanup of files we touch for style
> cleanup.
>
> You can check some style errors via:
>
> scripts/checkpatch.pl --file arch/x86/kernel/alternative.c
>
> but it also makes sense to look at the file and figure out places that
> look ugly.
>
>> x86: kernel/alternative.c cleanup
>
> total: 4 errors, 15 warnings, 4 checks, 540 lines checked
>
>> x86: kernel/apm_32.c cleanup
>
> total: 6 errors, 27 warnings, 5 checks, 2416 lines checked
>
> [ etc. ]
>
> If we did each style problem separately we'd be generating over 1
> million commits for the entire tree - that's not feasible. So we go per
> file and once a file has been cleaned up, we keep it clean.
>
> Note, checkpatch errors can be false positives occasionally, and not all
> warnings have to be fixed all the time - ask if unsure about whether to
> fix something or not.
>
> It's also useful to check that the .o's are unchanged after a cleanup.
> You can see commits that do that, for example:
Right. I will do this.
Thanks, Ingo.
>
> commit d4413732b54a17684e48fbb4b52fade5bf965b5d
> Author: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> Date: Tue Feb 19 23:51:27 2008 +0100
>
> x86: coding style fixes to arch/x86/oprofile/op_model_athlon.c
>
> The patch fixes 33 errors and a few warnings reported by checkpatch.pl
>
> arch/x86/oprofile/op_model_athlon.o:
> text data bss dec hex filename
> 1691 0 32 1723 6bb op_model_athlon.o.before
> 1691 0 32 1723 6bb op_model_athlon.o.after
> md5:
> c354bc2d7140e1e626c03390eddaa0a6 op_model_athlon.o.before.asm
> c354bc2d7140e1e626c03390eddaa0a6 op_model_athlon.o.after.asm
>
> Signed-off-by: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
> Ingo
>
--
----------------------------------------------
Gustavo Fernando Padovan
Engenharia de Computação 2006
LAS - Laboratório de Administração e Segurança de Sistemas
Instituto de Computação - UNICAMP
gfpadovan@gmail.com
ra061316@students.ic.unicamp.br
pao@jabber.org
-------------------------------------------
Seja Livre, use Software Livre
prev parent reply other threads:[~2008-07-28 21:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 21:09 Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 01/24] x86: kernel/alternative.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 02/24] x86: kernel/apm_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 03/24] x86: kernel/asm-offsets_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 04/24] x86: kernel/efi.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 05/24] x86: kernel/cpuid.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 06/24] x86: kernel/early-quirks.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 07/24] x86: kernel/io_apic_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 08/24] x86: kernel/io_apic_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 09/24] x86: kernel/irq_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 10/24] x86: kernel/irqinit_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 11/24] x86: kernel/kprobes.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 12/24] x86: kernel/microcode.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 13/24] x86: kernel/module_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 14/24] x86: kernel/pci-calgary_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 15/24] x86: kernel/probe_roms_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 16/24] x86: kernel/process_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 17/24] x86: kernel/process_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 18/24] x86: kernel/signal_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 19/24] x86: kernel/traps_64.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 20/24] x86: kernel/tsc.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 21/24] x86: kernel/visws_quirks.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 22/24] x86: kernel/vmi_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 23/24] x86: kernel/vmiclock_32.c cleanup Gustavo F. Padovan
2008-07-28 21:09 ` [PATCH 24/24] x86: kernel/sys_x86_64.c cleanup Gustavo F. Padovan
2008-07-29 1:47 ` [PATCH 11/24] x86: kernel/kprobes.c cleanup Masami Hiramatsu
2008-08-07 9:47 ` [PATCH 02/24] x86: kernel/apm_32.c cleanup Robert Richter
2008-07-28 21:17 ` [PATCH 0/24] x86: arch/x86/kernel/ cleanups Jeremy Fitzhardinge
2008-07-28 21:20 ` Ingo Molnar
2008-07-28 21:37 ` Gustavo F. Padovan [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=6b53b1990807281437l707be573n3be4d85feb033c63@mail.gmail.com \
--to=gustavo@las.ic.unicamp.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®