public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Rajesh Shah <rajesh.shah@intel.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: BUG 2.6.14.2 : ACPI boot lockup
Date: Tue, 22 Nov 2005 18:12:43 -0800	[thread overview]
Message-ID: <20051122181242.A5214@unix-os.sc.intel.com> (raw)
In-Reply-To: <20051123020609.GA30491@bougret.hpl.hp.com>; from jt@hpl.hp.com on Tue, Nov 22, 2005 at 06:06:09PM -0800

On Tue, Nov 22, 2005 at 06:06:09PM -0800, Jean Tourrilhes wrote:
> 
> 	This patch does not look right to me, but I must admit I have
> no clue about what the code is doing. Can you confirm you want me to
> try this ?
> 
Yes, please try this since this is known to fix at least a couple
of other machines (see 
https://bugzilla.novell.com/show_bug.cgi?id=116763)

The original acpi code ignored errors related to matching an
acpi device to an acpi driver. I changed that behavior to flag
an error, and this was wrong. An acpi device listed in the
namespace should not be required to have a driver for it to
be added to the acpi list.

thanks,
Rajesh

  reply	other threads:[~2005-11-23  2:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 21:19 BUG 2.6.14.2 : ACPI boot lockup Jean Tourrilhes
2005-11-23  0:54 ` Rajesh Shah
2005-11-23  2:06   ` Jean Tourrilhes
2005-11-23  2:12     ` Rajesh Shah [this message]
2005-11-23  2:25       ` Jean Tourrilhes
2005-11-23  6:08         ` Henrik Persson
2005-11-23  8:00   ` Jani Monoses
  -- strict thread matches above, loose matches on Subject: below --
2005-11-22 23:35 Jean Tourrilhes
2005-11-22 21:14 Jean Tourrilhes
2005-11-22 19:08 Jean Tourrilhes
2005-11-22 20:15 ` Jani Monoses

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=20051122181242.A5214@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=jt@hpl.hp.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