From: Dan Chen <crimsun@email.unc.edu>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DEVFS broken?
Date: Sun, 20 Jan 2002 19:45:59 -0500 [thread overview]
Message-ID: <20020121004559.GA487@opeth.ath.cx> (raw)
In-Reply-To: <20020117171229.GA1084@the-penguin.otak.com> <20020117190449.GA2860@opeth.ath.cx> <200201202004.g0KK4aN13185@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201202004.g0KK4aN13185@vindaloo.ras.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Working well so far: booted and no oopses yet. Thanks!
On Sun, Jan 20, 2002 at 01:04:36PM -0700, Richard Gooch wrote:
> Please apply this patch on top of devfs-patch-v199.7 or on top of
> plain 2.5.2, and let me know the result.
--
Dan Chen crimsun@email.unc.edu
GPG key: www.unc.edu/~crimsun/pubkey.gpg.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-21 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 17:12 DEVFS broken? Lawrence Walton
2002-01-17 19:04 ` Dan Chen
2002-01-20 20:04 ` Richard Gooch
2002-01-21 0:00 ` Dan Chen
2002-01-21 0:45 ` Dan Chen [this message]
[not found] ` <200201210050.g0L0oQm17429@vindaloo.ras.ucalgary.ca>
2002-01-21 17:38 ` Dan Chen
2002-01-18 10:12 ` Helge Hafting
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=20020121004559.GA487@opeth.ath.cx \
--to=crimsun@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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