From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Kent Yoder'" <key@austin.ibm.com>, linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: RE: Oops on 2.5.39 was Re: [PATCH] pcnet32 cable status check
Date: Mon, 30 Sep 2002 15:00:43 -0700 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD0236DEE1@orsmsx119.jf.intel.com> (raw)
Whups that's mine.
I'll get a fix out today.
-- Andy
> From: Kent Yoder [mailto:key@austin.ibm.com]
[.. Linux NET starting.. other ACPI info ..]
ACPI Namespace successfully loaded at root c053f4bc
<freeze>
Kent
next reply other threads:[~2002-09-30 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 22:00 Grover, Andrew [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 20:21 [PATCH] pcnet32 cable status check Jeff Garzik
2002-09-30 21:48 ` Oops on 2.5.39 was " Kent Yoder
2002-09-30 21:55 ` Jeff Garzik
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=EDC461A30AC4D511ADE10002A5072CAD0236DEE1@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=jgarzik@pobox.com \
--cc=key@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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).