From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-acpi <linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Diefenbaugh,
Paul S"
<paul.s.diefenbaugh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: RE: ACPI vs. ISA IRQs
Date: Wed, 5 Nov 2003 00:09:53 +0000 [thread overview]
Message-ID: <20031105000953.GN14749@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470255EF8A-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
On Tue, Nov 04, 2003 at 03:28:54PM -0800, Grover, Andrew wrote:
> > From: Brown, Len
> > Assumption: sharing interrupts is bad.
> > How to fix?
I would ask Linus. He tends to have pretty strong opinions on how
this kind of thing should be done.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-11-05 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 23:28 ACPI vs. ISA IRQs Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470255EF8A-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-11-05 0:09 ` Matthew Wilcox [this message]
2003-11-05 6:51 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2003-11-05 7:30 Grover, Andrew
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=20031105000953.GN14749@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=paul.s.diefenbaugh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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