public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Arch list <linux-arch@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] Add NO_IRQ to all architectures
Date: Mon, 25 Oct 2004 19:17:46 -0700	[thread overview]
Message-ID: <20041026021746.GC17038@holomorphy.com> (raw)
In-Reply-To: <1098756491.17886.18.camel@gaston>

On Tue, Oct 26, 2004 at 12:08:11PM +1000, Benjamin Herrenschmidt wrote:
> Here'd a patch adding a definition of NO_IRQ to all archs
include/asm-*/irq.h. This patch currently defines it to (-1) for all
> archs. IRQ numbers are randomly stored in int's, unsigned int's, or
> all sort of things all over the kernel, but that shouldn't be a
> problem in most cases. NO_IRQ is mostly to be used within a given
> driver, to identify a device for which it has no IRQ assigned. This
> concerns relatively few drivers, like 8250 or IDE.
> At this point, I do _not_ intend to fix the probe_irq_*() API to
> return NO_IRQ instead of 0, that could be done in a second step (or
> x86 NO_IRQ could simply be defined to be 0 ...), but I will fix IDE
> in a subsequent patch.
> It would be nice though if things could slowly get fixed to deal with
> it in a better way.

Maybe wrapping the numbers in a struct for strict typechecking given
some config option, eventually making it mandatory once enough drivers
are swept would make sense.


-- wli

  reply	other threads:[~2004-10-26  2:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26  2:08 [RFC] Add NO_IRQ to all architectures Benjamin Herrenschmidt
2004-10-26  2:17 ` William Lee Irwin III [this message]
2004-10-26  2:27 ` Linus Torvalds
2004-10-26  2:31   ` Benjamin Herrenschmidt
2004-10-26  2:41     ` William Lee Irwin III
2004-10-26  8:24     ` David Woodhouse

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=20041026021746.GC17038@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-arch@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