public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Shaohua Li <shaohua.li@intel.com>, Len Brown <lenb@kernel.org>,
	"Barnes, Jesse" <jesse.barnes@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-pci@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 02:08:57 -0800	[thread overview]
Message-ID: <4B309AB9.7030208@kernel.org> (raw)
In-Reply-To: <20091218051457.GB417@elte.hu>

Ingo Molnar wrote:
> * Shaohua Li <shaohua.li@intel.com> wrote:
> 
>> On Fri, Dec 18, 2009 at 09:28:50AM +0800, Yinghai Lu wrote:
>>> On Wed, Dec 16, 2009 at 12:06 PM, Len Brown <lenb@kernel.org> wrote:
>>>> Hi Linus,
>>>>
>>>> please pull from:
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
>>>>
>>> ;..
>>>> Shaohua Li (3):
>>>> ? ? ?ACPI: Add a generic API for _OSC -v2
>>>> ? ? ?ACPI: cleanup pci_root _OSC code.
>>>> ? ? ?ACPI: Add platform-wide _OSC support.
>>> it seems these three patches broke the _OSC on my intel new systems.
>>>
>>> revert them fix the problem with AER and pciehp and etc
>> can you give more details? I just cleaned up the _OSC code for AER and 
>> pciehp, no function changes.
> 
> Famous last words ;-)
> 
> Yinghai, i suspect Shaohua needs the kind of info you'd need if you tried to 
> fix it: acpidump, before/after debug boot log, a description of what goes bad, 
> etc.

the so called clean up, change the ret length checking.

-       if (!output.length)
-               return AE_NULL_OBJECT;
-

+       /* return buffer should have the same length as cap buffer */
+       if (context->ret.length != context->cap.length)
+               return AE_NULL_OBJECT;

YH

  reply	other threads:[~2009-12-22 10:10 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 [this message]
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
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=4B309AB9.7030208@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