From: John Fremlin <vii@users.sourceforge.net>
To: Jeff Golds <jgolds@resilience.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Problems with arch/i386/kernel/apm.c
Date: 11 Jun 2001 20:37:58 +0100 [thread overview]
Message-ID: <m266e2lsdl.fsf@boreas.yi.org.> (raw)
In-Reply-To: <3B25068B.53F2968A@resilience.com>
In-Reply-To: <3B25068B.53F2968A@resilience.com> (Jeff Golds's message of "Mon, 11 Jun 2001 10:57:31 -0700")
Jeff Golds <jgolds@resilience.com> writes:
[...]
> Please let me know if this is correct, I can provide a simple patch
> if needed. What I am really desiring to know is if there are any
> devices that depend on the apm::send_event(APM_NORMAL_RESUME)
> happening while interrupts are disabled.
Yes, USB host controllers
--
http://ape.n3.net
prev parent reply other threads:[~2001-06-11 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 17:57 Jeff Golds
2001-06-11 18:11 ` Jeff Garzik
2001-06-11 18:42 ` Alan Cox
2001-06-12 23:48 ` Patrick Mochel
2001-06-14 8:18 ` Alan Cox
2001-06-11 19:37 ` John Fremlin [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=m266e2lsdl.fsf@boreas.yi.org. \
--to=vii@users.sourceforge.net \
--cc=jgolds@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: Problems with arch/i386/kernel/apm.c' \
/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
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).