From: Chris Wright <chrisw@osdl.org>
To: Andreas Schwarz <usenet.2117@andreas-s.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Call traces due to lost IRQ
Date: Tue, 30 Sep 2003 13:59:34 -0700 [thread overview]
Message-ID: <20030930135934.B722@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <slrnbnjksd.3pa.usenet.2117@home.andreas-s.net>; from usenet.2117@andreas-s.net on Tue, Sep 30, 2003 at 07:03:28PM +0000
* Andreas Schwarz (usenet.2117@andreas-s.net) wrote:
> This solved the issue for me.
Great, although I'm a bit confused. In your last mail you said you were
using 2.6.0-test6-mm1. That patch is already in mm1, so were you using
plain 2.6.0-test6 by any chance?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2003-09-30 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:40 Call traces due to lost IRQ Martin Pitt
2003-09-30 16:47 ` Andreas Schwarz
2003-09-30 17:28 ` Sergey S. Kostyliov
2003-09-30 18:24 ` Chris Wright
2003-09-30 19:03 ` Andreas Schwarz
2003-09-30 20:59 ` Chris Wright [this message]
2003-10-01 9:54 ` Andreas Schwarz
2003-09-30 22:24 ` Martin Pitt
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=20030930135934.B722@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usenet.2117@andreas-s.net \
/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).