From: Greg KH <gregkh@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>, rajesh.shah@intel.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Matthew Wilcox <matthew@wil.cx>,
"Brown, Len" <len.brown@intel.com>
Subject: Re: [2.6.15-rc4] oops in acpiphp
Date: Fri, 2 Dec 2005 13:46:55 -0800 [thread overview]
Message-ID: <20051202214655.GA13599@suse.de> (raw)
In-Reply-To: <4390B646.60709@pobox.com>
On Fri, Dec 02, 2005 at 04:01:58PM -0500, Jeff Garzik wrote:
>
> Booting with acpiphp on this dual core, dual package (2x2) box causes an
> oops.
Ok, I've heard about this one before, in looking closer at this. Rajesh
is aware of this one (right Rajesh? I'll bounce you the original
message). I'll let him take it from here...
thanks,
greg k-h
next prev parent reply other threads:[~2005-12-02 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 21:01 [2.6.15-rc4] oops in acpiphp Jeff Garzik
2005-12-02 21:40 ` Greg KH
2005-12-02 21:48 ` Jeff Garzik
2005-12-02 21:45 ` Rajesh Shah
2005-12-02 21:46 ` Greg KH [this message]
2005-12-02 21:57 ` Rajesh Shah
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=20051202214655.GA13599@suse.de \
--to=gregkh@suse.de \
--cc=jgarzik@pobox.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rajesh.shah@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