From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: Tree for August 14 (sysfs/acpi errors)
Date: Thu, 25 Sep 2008 12:39:29 +1000
Message-ID: <200809251239.30416.rusty@rustcorp.com.au>
References: <20080814172945.250a27f2.sfr@canb.auug.org.au> <200808171513.13611.rusty@rustcorp.com.au> <alpine.LFD.1.10.0809240353520.20067@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-acpi-owner@vger.kernel.org>
In-Reply-To: <alpine.LFD.1.10.0809240353520.20067@localhost.localdomain>
Content-Disposition: inline
Sender: linux-acpi-owner@vger.kernel.org
To: Len Brown <lenb@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>, Greg KH <greg@kroah.com>, Kay Sievers <kay.sievers@vrfy.org>, Randy Dunlap <randy.dunlap@oracle.com>, Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, linux-acpi@vger.kernel.org
List-Id: linux-next.vger.kernel.org

On Wednesday 24 September 2008 17:59:41 Len Brown wrote:
> This problem first shows up with the addition of the
> acpi.power_nocheck modparam, which is staged for 2.6.28.
> Is 2.6.28 "current" or longer term?

There's a proper fix in linux-next for 2.6.28.  I was unclear about whether 
this ACPI change was going into 2.6.27; since it's not, there's no real 
issue.

Hope that helps,
Rusty.