From: Pantelis Antoniou <panto@intracom.gr>
To: linuxppc-embedded@lists.linuxppc.org,
Tom Rini <trini@kernel.crashing.org>,
Dan Malek <dan@embeddededge.com>
Subject: 2.5 and request_8xxirq
Date: Wed, 15 Jan 2003 12:25:57 +0200 [thread overview]
Message-ID: <3E253735.8040300@intracom.gr> (raw)
Hi
I'm in the process of porting my board based on a MPC850
from 2.4 to 2.5 and it appears that request_8xxirq is gone.
There was some previous discussion about this subject and
some patches were presented by Tom. Apparently there were
some objections and are not in the kernel.
Is it safe to use them? And if not what is the proper
way to address this problem?
Regards
Pantelis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-01-15 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 10:25 Pantelis Antoniou [this message]
2003-01-15 14:43 ` 2.5 and request_8xxirq Allen Curtis
2003-01-15 15:13 ` Pantelis Antoniou
2003-01-15 22:26 ` Tom Rini
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=3E253735.8040300@intracom.gr \
--to=panto@intracom.gr \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).