From: Cort Dougan <cort@fsmlabs.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Question about IRQ_PENDING/IRQ_REPLAY
Date: Sun, 4 Mar 2001 23:07:07 -0700 [thread overview]
Message-ID: <20010304230707.L2565@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <20010303144856.A18389@ftsoj.fsmlabs.com> <19350127143809.22288@smtp.wanadoo.fr>
In-Reply-To: <19350127143809.22288@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Sun, Mar 04, 2001 at 10:06:25PM +0100
} Also, we currently don't use the same mecanism as i386, and since Linus
} expressed his desire to have irq.c become generic, I'm trying to make sure
} I fully understand it before merging in PPC the bits that I didn't merge
} them yet.
More generic in terms of using irq_desc[] and some similar structures I can
see. Making do_IRQ() and enable/disable use the same names and structures
as x86 isn't sensible. They're different ports, with different design
philosophies.
I don't believe that the plan is a common irq.c - lets stay away from that.
next prev parent reply other threads:[~2001-03-05 6:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 7:20 Question about IRQ_PENDING/IRQ_REPLAY Benjamin Herrenschmidt
2001-03-03 18:00 ` Linus Torvalds
2001-03-03 21:48 ` Cort Dougan
2001-03-04 21:06 ` Benjamin Herrenschmidt
2001-03-05 6:07 ` Cort Dougan [this message]
2001-03-05 9:48 ` Benjamin Herrenschmidt
2001-03-05 10:00 ` Benjamin Herrenschmidt
2001-03-05 18:15 ` Linus Torvalds
2001-03-05 21:00 ` Cort Dougan
2001-03-05 21:47 ` Benjamin Herrenschmidt
2001-03-05 21:39 ` Benjamin Herrenschmidt
2001-03-04 12:36 ` Benjamin Herrenschmidt
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=20010304230707.L2565@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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