linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Allen Curtis" <acurtis@onz.com>
To: "Paul Mackerras" <paulus@au1.ibm.com>, <markc@mail.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: undefined IRQs in request_irq
Date: Thu, 19 Sep 2002 06:46:40 -0700	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFAEFADMAA.acurtis@onz.com> (raw)
In-Reply-To: <15753.7943.294858.151802@argo.ozlabs.ibm.com>


> No.  IMO the current request_8xxirq / request_irq stuff is completely
> bogus.  I can understand it as a temporary construction while
> debugging stuff, but it has long outlived its usefulness.  We should
> just use request_irq for everything, request_8xxirq should die.

Multiple people have submitted patches to fix this but they have not made it
into the release code. What can be done?


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-09-19 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 14:39 undefined IRQs in request_irq Mark Chambers
2002-09-19  0:49 ` Paul Mackerras
2002-09-19 13:46   ` Allen Curtis [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=NCBBIINEHIPFGJPLBEIFAEFADMAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=markc@mail.com \
    --cc=paulus@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).