public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Len Brown <lenb@kernel.org>
Cc: Shaohua Li <shaohua.li@intel.com>, Ingo Molnar <mingo@elte.hu>,
	"Barnes, Jesse" <jesse.barnes@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-acpi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [git pull request] ACPI and driver patches for 2.6.33.merge
Date: Tue, 22 Dec 2009 12:44:25 -0800	[thread overview]
Message-ID: <4B312FA9.1020301@kernel.org> (raw)
In-Reply-To: <4B312F09.5020602@kernel.org>

Yinghai Lu wrote:
> 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.
> 

with following change, AER could be loaded, but pciehp still can not be loaded.

---
 drivers/acpi/bus.c |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Index: linux-2.6/drivers/acpi/bus.c
===================================================================
--- linux-2.6.orig/drivers/acpi/bus.c
+++ linux-2.6/drivers/acpi/bus.c
@@ -424,7 +424,9 @@ acpi_status acpi_run_osc(acpi_handle han
 		return status;
 
 	/* return buffer should have the same length as cap buffer */
-	if (context->ret.length != context->cap.length)
+	printk(KERN_INFO "run_acpi_osc: ret length %d cap length %d\n",
+			 context->ret.length, context->cap.length);
+	if (context->ret.length < context->cap.length)
 		return AE_NULL_OBJECT;
 
 	out_obj = context->ret.pointer;

  reply	other threads:[~2009-12-22 20:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 20:06 [git pull request] ACPI and driver patches for 2.6.33.merge Len Brown
2009-12-18  1:28 ` Yinghai Lu
2009-12-18  2:21   ` Shaohua Li
2009-12-18  5:14     ` Ingo Molnar
2009-12-22 10:08       ` Yinghai Lu
2009-12-22 10:31         ` Yinghai Lu
2009-12-23  0:56         ` Shaohua Li
2009-12-23  1:38           ` Yinghai Lu
2009-12-23  2:09             ` Yinghai Lu
2009-12-23  2:45               ` Shaohua Li
2009-12-23  2:57                 ` Yinghai Lu
2009-12-23  9:04                   ` Shaohua Li
2009-12-22  2:10   ` Len Brown
2009-12-22  2:57     ` Yinghai Lu
2009-12-22  7:54       ` Len Brown
2009-12-22  7:59         ` Yinghai Lu
2009-12-22 19:45           ` Len Brown
2009-12-22 20:41             ` Yinghai Lu
2009-12-22 20:44               ` Yinghai Lu [this message]
2009-12-23 22:46                 ` Len Brown

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=4B312FA9.1020301@kernel.org \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=jesse.barnes@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@linux-foundation.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