From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Add support for checking before-the-fact whether an IRQ is
Date: Tue, 30 Dec 2003 13:47:03 +1100 [thread overview]
Message-ID: <20031230134703.71379d63.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.58.0312291140360.2113@home.osdl.org>
On Mon, 29 Dec 2003 11:43:29 -0800 (PST)
Linus Torvalds <torvalds@osdl.org> wrote:
> > question; which lock prevents someone else claiming the irq and making
> > it unsharable/unclaimable between can_request_irq() and the eventual
> > request_irq() ????
>
> Nothing. It never did. This is basically a heuristic: "find the irq that
> looks the least used".
I just worry about other people using it. I'd prefer "irq_looks_free()",
but since it's x86-specific it's not a big issue.
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
prev parent reply other threads:[~2003-12-30 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312291905.hBTJ56k1032326@hera.kernel.org>
2003-12-29 19:18 ` Arjan van de Ven
2003-12-29 19:43 ` Linus Torvalds
2003-12-30 2:47 ` Rusty Russell [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=20031230134703.71379d63.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=arjanv@redhat.com \
--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
Powered by JetHome