public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-acpi@vger.kernel.org, lenb@kernel.org
Subject: Re: [RESEND] [PATCH 2/4]  ACPI: Get the device power state in the course of scanning device
Date: Mon, 11 Aug 2008 12:48:59 +0200	[thread overview]
Message-ID: <20080811104859.GN9038@one.firstfloor.org> (raw)
In-Reply-To: <1218450075.6671.135.camel@yakui_zhao.sh.intel.com>

On Mon, Aug 11, 2008 at 06:21:15PM +0800, Zhao Yakui wrote:
> On Mon, 2008-08-11 at 09:56 +0200, Andi Kleen wrote:
> > > After the patch is applied, Linux will still do the power state check
> > > unless the boot option of "acpi.power_nocheck=1" is added.  In such case
> > > it won't affect anything. 
> > 
> > Understood that.
> > 
> > > In fact we expect that the boot option of "acpi.power_nocheck=1" becomes
> > > the default. But we will have to wait for more response. Only after more
> > > tests are done, it will be OK.
> > 
> > Ok. 
> > 
> > > what the init sequence ordering for .27 means? 
> > 
> > The first patch moved acpi_device_set_context to be earlier, so 
> > the init sequence is different. All the other changes are optional,
> > as in conditional on the flag, but that one is not.
> Although the acpi_device_set_context is moved to the earlier in the
> first patch, it won't break anything.

Well they always say that :) But I'll double check.

-Andi

  reply	other threads:[~2008-08-11 10:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  6:55 [RESEND] [PATCH 2/4] ACPI: Get the device power state in the course of scanning device Zhao Yakui
2008-08-11  6:45 ` Andi Kleen
2008-08-11  7:02   ` Zhao Yakui
2008-08-11  6:52     ` Andi Kleen
2008-08-11  7:51       ` Zhao Yakui
2008-08-11  7:56         ` Andi Kleen
2008-08-11 10:21           ` Zhao Yakui
2008-08-11 10:48             ` Andi Kleen [this message]
2008-08-11 11:54               ` Rafael J. Wysocki

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=20080811104859.GN9038@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@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