From: David Howells <dhowells@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] frv: Remove bogus NO_IRQ = -1 define
Date: Wed, 07 Nov 2007 17:28:22 +0000 [thread overview]
Message-ID: <30708.1194456502@redhat.com> (raw)
In-Reply-To: <20071107165300.6eeea2d8@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> The old NO_IRQ define some platforms had was long ago declared obsolete
> and wrong. FRV should therefore not be re-introducing this, especially as
> IRQs are usually unsigned in the kernel. The "no IRQ" case is defined to be
> zero and Linus made this rather clear at the time.
>
> arch/frv shows no dependancy on this but it might show up driver fixes
> needing doing I guess
FRV doesn't use IRQ 0, so using 0 instead is fine.
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2007-11-07 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 16:53 [PATCH] frv: Remove bogus NO_IRQ = -1 define Alan Cox
2007-11-07 17:28 ` David Howells [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=30708.1194456502@redhat.com \
--to=dhowells@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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