From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: hpa <hpa@zytor.com>, tglx <tglx@linutronix.de>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [PATCH] x86: coding style fixes to arch/x86/kernel/io_apic_32.c
Date: Mon, 9 Jun 2008 22:59:28 +0200 [thread overview]
Message-ID: <4d8e3fd30806091359p1cda5e45o206160c76a7f5bc5@mail.gmail.com> (raw)
In-Reply-To: <20080609190204.GA13674@elte.hu>
On Mon, Jun 9, 2008 at 9:02 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
>
>> Before:
>> total: 91 errors, 73 warnings, 2850 lines checked
>>
>> After:
>> total: 1 errors, 47 warnings, 2848 lines checked
>
> applied, thanks. A small detail:
Thank you. Did you manage to look/apply the other two patches as well?
http://lkml.org/lkml/2008/6/7/64
http://lkml.org/lkml/2008/6/7/62
The latter might suffer for the same problem you fixed with the below patch.
>> +++ b/arch/x86/kernel/io_apic_32.c
>> @@ -37,12 +37,12 @@
>> #include <linux/kthread.h>
>> #include <linux/jiffies.h> /* time_after() */
>>
>> -#include <asm/io.h>
>> -#include <asm/smp.h>
>> +#include <linux/io.h>
>> +#include <linux/smp.h>
>
> i suspect checkpatch suggested that asm/smp.h -> linux/smp.h change, but
> there was a subtle detail here - asm/smp.h has dual role on x86, it also
> carries a fair number of low level details about APIC/SMP details -
> which matters on UP IOAPIC.
You are right.
Sorry for not catching that.
BTW, I'm a bit lost in all the branches you are managing in the tip tree :-)
Which one should I look at to notice when the patches are applied?
Thanks.
Regards,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/
next prev parent reply other threads:[~2008-06-09 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-08 11:07 Paolo Ciarrocchi
2008-06-09 19:02 ` Ingo Molnar
2008-06-09 20:59 ` Paolo Ciarrocchi [this message]
2008-06-10 10:43 ` 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=4d8e3fd30806091359p1cda5e45o206160c76a7f5bc5@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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®