[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B312F09.5020602@kernel.org>
Date: Tue, 22 Dec 2009 12:41:45 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Len Brown <lenb@...nel.org>
CC: Shaohua Li <shaohua.li@...el.com>, Ingo Molnar <mingo@...e.hu>,
"Barnes, Jesse" <jesse.barnes@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-pci@...r.kernel.org
Subject: Re: [git pull request] ACPI and driver patches for 2.6.33.merge
Len Brown wrote:
> On Mon, 21 Dec 2009, Yinghai Lu wrote:
>
>> Len Brown wrote:
>>> Does 3563ff964fdc36358cef0330936fdac28e65142a work or fail on your system?
>>> I didn't ask about reverting it, I asked if it works or fails.
>> i don't know.
>>
>> anything i should search in the bootlog?
>
> Please check out a branch at the commit identified above
> and tell us if the following issue:
>
> "it seems these three patches broke the _OSC on my intel new systems."
>
> "revert them fix the problem with AER and pciehp and etc"
>
> is present or absent on that branch.
>
> If the answer is yes, when stock 2.6.32 works, then the 3 patches
> between that commit and 2.6.32 are at fault. If the answer is no,
> yet reverting those patches helps top of tree, then the issue must
> be a merge conflict with other changes in 2.6.33.
8aedf8a6ae98d5d4df3254b6afb7e4432d9d8600
the one just before acpi release was merged to mainline
<fter pci merge...>
it works.
YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists