From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: David Miller <davem@davemloft.net>,
xiyou.wangcong@gmail.com, x86@kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com
Subject: Re: [PATCH] irq: handle irq0 special only on x86
Date: Wed, 16 Dec 2009 15:04:27 +0100 [thread overview]
Message-ID: <20091216140427.GD3674@pengutronix.de> (raw)
In-Reply-To: <4B21246B.4070804@zytor.com>
On Thu, Dec 10, 2009 at 08:40:11AM -0800, H. Peter Anvin wrote:
> On 12/10/2009 12:24 AM, Uwe Kleine-König wrote:
> >
> > Note, I fully agree to use 0 for NO_IRQ if you have an int-sized value
> > that holds either NO_IRQ or a valid irq number. But in practise I'd not
> > recommend to use this idiom.
> >
>
> You're tilting at windmills about something that was settled long ago,
> like it or not.
And what about the patch, not judging my comments about irq0 in general?
AFAICT the check in try_misrouted_irq for irq being not zero does only
make sense on x86, doesn't it?
The comment a few lines above the check reads:
But for 'irqfixup == 2' we also do it for handled interrupts if
they are marked as IRQF_IRQPOLL (or for irq zero, which is the
traditional PC timer interrupt.. Legacy)
So I think the patch is justified.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-12-16 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 9:20 [PATCH] irq: handle irq0 special only on x86 Uwe Kleine-König
2009-12-09 9:28 ` Américo Wang
2009-12-09 9:35 ` Uwe Kleine-König
2009-12-09 9:41 ` David Miller
2009-12-10 8:24 ` Uwe Kleine-König
2009-12-10 16:40 ` H. Peter Anvin
2009-12-13 0:34 ` Maciej W. Rozycki
2009-12-16 14:04 ` Uwe Kleine-König [this message]
2010-01-12 15:59 ` Uwe Kleine-König
2010-01-13 4:59 ` 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=20091216140427.GD3674@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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