From: Linus Torvalds <torvalds@transmeta.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: <linux-kernel@vger.kernel.org>,
"Diefenbaugh, Paul S" <paul.s.diefenbaugh@intel.com>
Subject: RE: Oops in 2.5.7-pre2: ACPI?
Date: Mon, 18 Mar 2002 11:07:36 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.33.0203181106590.17467-100000@home.transmeta.com> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C02AB7D07@orsmsx111.jf.intel.com>
On Mon, 18 Mar 2002, Grover, Andrew wrote:
>
> I can see from bkbits looks like you already fixed it post-pre2, so I guess
> we will just sit tight and everything will be fine once pre3 is out.
I haven't much tested my fixes, but I hope it's close enough to be
workable.
Linus
next prev parent reply other threads:[~2002-03-18 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 18:43 Oops in 2.5.7-pre2: ACPI? Grover, Andrew
2002-03-18 19:07 ` Linus Torvalds [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-16 21:33 Alex Walker
2002-03-16 23:02 ` Miles Lane
2002-03-16 23:25 ` Linus Torvalds
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=Pine.LNX.4.33.0203181106590.17467-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.s.diefenbaugh@intel.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 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).