From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: x86 maintainers <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: apic/io_apic fix compilation warning
Date: Sat, 21 Mar 2009 17:36:42 +0100 [thread overview]
Message-ID: <20090321163642.GI11183@elte.hu> (raw)
In-Reply-To: <1237630967.2409.1.camel@ht.satnam>
* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> Hello Ingo,
>
> Is this fix looks OK to you:
>
> From: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> Date: Sat, 21 Mar 2009 15:41:17 +0530
> Subject: [PATCH] x86: apic/io_apic fix compilation warning
>
> Fix:
> arch/x86/kernel/apic/io_apic.c:1431: warning: ‘msi_ir_chip’ defined but not used
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> ---
> arch/x86/kernel/apic/io_apic.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/apic/io_apic.c b/arch/x86/kernel/apic/io_apic.c
> index d882c03..3ca7838 100644
> --- a/arch/x86/kernel/apic/io_apic.c
> +++ b/arch/x86/kernel/apic/io_apic.c
> @@ -1428,7 +1428,6 @@ void __setup_vector_irq(int cpu)
>
> static struct irq_chip ioapic_chip;
> static struct irq_chip ir_ioapic_chip;
> -static struct irq_chip msi_ir_chip;
>
> #define IOAPIC_AUTO -1
> #define IOAPIC_EDGE 0
> @@ -3402,6 +3401,8 @@ static struct irq_chip msi_ir_chip = {
> #endif
> .retrigger = ioapic_retrigger_irq,
> };
> +#else
> +static struct irq_chip msi_ir_chip;
> #endif
hm, i think it would be cleaner to remove the CONFIG_INTR_REMAP
define altogether and define msi_ir_chip all the time. (and make
sure this build fine even in the !INTR_REMAP case)
Ingo
next prev parent reply other threads:[~2009-03-21 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 10:22 Jaswinder Singh Rajput
2009-03-21 16:36 ` Ingo Molnar [this message]
2009-03-21 18:20 ` Jaswinder Singh Rajput
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=20090321163642.GI11183@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®