From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: [PATCH and RFC] Remove request_8xxirq
Date: Sun, 23 Jun 2002 18:54:43 +0200 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJCEOKCFAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <15635.16331.965632.877856@argo.ozlabs.ibm.com>
Hi,
why not simply placing a new request_cascaded_irq() with an additional
controller/device identifier beside request_irq().
If you map the functionality to the original functions the rest of the code
could stay unchanged.
You can even map the old function calls using macros.
(If you like to you can use device 0 for a virtual mapping too. But I
wouldn't. :)
request_irq() could be left unchanged and new patches could use a single
registration function. So everyone should stay happy.
Stephan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-06-23 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15635.16331.965632.877856@argo.ozlabs.ibm.com>
2002-06-23 16:54 ` Stephan Linke [this message]
2002-06-21 2:32 [PATCH and RFC] Remove request_8xxirq Andy Lowe
2002-06-21 4:35 ` Dan Malek
2002-06-21 4:54 ` Andy Lowe
[not found] <3D124DF4.6060505@embeddededge.com>
2002-06-20 22:02 ` Wolfgang Denk
[not found] <20020620214551.GI16052@opus.bloom.county>
2002-06-20 21:58 ` Wolfgang Denk
[not found] ` <20020620221016.GK16052@opus.bloom.county>
[not found] ` <3D12F667.30902@bluewin.ch>
2002-06-24 17:00 ` Tom Rini
2002-06-24 17:49 ` Dan Malek
2002-06-24 17:59 ` Tom Rini
[not found] ` <3D1793E1.3030509@bluewin.ch>
[not found] ` <20020624224100.GL3489@opus.bloom.county>
2002-06-25 0:03 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 20:34 Tom Rini
2002-06-20 21:04 ` Dan Malek
2002-06-20 21:39 ` Tom Rini
2002-06-20 22:03 ` Dan Malek
2002-06-20 16:58 ` Benjamin Herrenschmidt
2002-06-20 22:34 ` Tom Rini
2002-06-20 21:16 ` Wolfgang Denk
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=FCEAKDJJAPHPLJFINDAJCEOKCFAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).