From: David Raufeisen <david@fortyoz.org>
To: rui.sousa@mindspeed.com
Cc: linux-kernel@vger.kernel.org, emu10k1-devel@opensource.creative.com
Subject: Re: [Emu10k1-devel] Re: how to crash 2.4.4 w/SBLive
Date: Thu, 31 May 2001 15:58:31 -0700 [thread overview]
Message-ID: <20010531155831.A14062@fortyoz.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0105312031070.17958-200000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0105312031070.17958-200000@localhost.localdomain>
Great,
No more oops.
Thanks
On Thursday, 31 May 2001, at 20:33:54 (+0200),
rui.sousa@mindspeed.com wrote:
> On Thu, 31 May 2001, David Raufeisen wrote:
>
> But now it progressed a bit more ;)
>
> New patch attached.
>
--
David Raufeisen <david@fortyoz.org>
Cell: (604) 818-3596
next prev parent reply other threads:[~2001-05-31 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 6:37 how to crash 2.4.4 w/SBLive John Lenton
2001-05-24 13:50 ` Bill Pringlemeir
2001-05-28 23:38 ` Bill Pringlemeir
2001-05-28 23:59 ` Keith Owens
2001-05-24 18:42 ` David Raufeisen
2001-05-31 10:01 ` rui.sousa
2001-05-31 17:59 ` David Raufeisen
2001-05-31 18:33 ` [Emu10k1-devel] " rui.sousa
2001-05-31 22:58 ` David Raufeisen [this message]
2001-06-01 4:01 ` John R Lenton
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=20010531155831.A14062@fortyoz.org \
--to=david@fortyoz.org \
--cc=emu10k1-devel@opensource.creative.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.sousa@mindspeed.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 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.