From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to avoid 'lost interrupt' messages post-resume?
Date: Fri, 02 Jan 2004 09:59:52 +1100 [thread overview]
Message-ID: <1072997992.1188.15.camel@gaston> (raw)
In-Reply-To: <1072984022.22058.3.camel@laptop-linux>
On Fri, 2004-01-02 at 06:07, Nigel Cunningham wrote:
> Thanks for the reply.
>
> I'll look into that area some more.
Let me know what you find, I may be able to help you getting
it right, though it' a bit difficult to do generically in 2.4
Ben.
prev parent reply other threads:[~2004-01-01 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 4:41 How to avoid 'lost interrupt' messages post-resume? Nigel Cunningham
2004-01-01 8:09 ` Benjamin Herrenschmidt
2004-01-01 19:07 ` Nigel Cunningham
2004-01-01 22:59 ` Benjamin Herrenschmidt [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=1072997992.1188.15.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.