linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: x86@kernel.org, linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] irq: handle irq0 special only on x86
Date: Tue, 12 Jan 2010 16:59:29 +0100	[thread overview]
Message-ID: <20100112155929.GA5615@pengutronix.de> (raw)
In-Reply-To: <1260350401-9858-1-git-send-email-u.kleine-koenig@pengutronix.de>

Hello,

On Wed, Dec 09, 2009 at 10:20:01AM +0100, Uwe Kleine-König wrote:
> I just noticed this when digging in the irq handling.  At least for arm
> this doesn't make sense.  Not sure if x86 is the only arch this test
> is valid for, but probably it is.
... so I added linux-arch@vger.kernel.org
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> ---
>  kernel/irq/spurious.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/irq/spurious.c b/kernel/irq/spurious.c
> index 22b0a6e..4996b66 100644
> --- a/kernel/irq/spurious.c
> +++ b/kernel/irq/spurious.c
> @@ -199,8 +199,10 @@ try_misrouted_irq(unsigned int irq, struct irq_desc *desc,
>  	if (irqfixup < 2)
>  		return 0;
>  
> +#if defined(CONFIG_ARCH_X86)
>  	if (!irq)
>  		return 1;
> +#endif
>  
>  	/*
>  	 * Since we don't get the descriptor lock, "action" can
the feed-back I have got up to now wasn't helpfull.  (Only some "irq0 is
evil---no it's not" discussion.) So what do you think?  I admit the
#ifdef isn't nice, but if the semantic is OK I'm willing to rework it
into something more pretty.

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

       reply	other threads:[~2010-01-12 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1260350401-9858-1-git-send-email-u.kleine-koenig@pengutronix.de>
2010-01-12 15:59 ` Uwe Kleine-König [this message]
2010-01-13  4:59   ` [PATCH] irq: handle irq0 special only on x86 H. Peter Anvin

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=20100112155929.GA5615@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).