public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: "Moore, Robert" <robert.moore@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	acpi <acpi@linux.intel.com>
Subject: Re: ACPICA Release 20081031 linuxized patch set
Date: Thu, 13 Nov 2008 15:54:56 +0800	[thread overview]
Message-ID: <1226562896.30025.176.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0811130230060.21141@localhost.localdomain>

On Thu, 2008-11-13 at 15:31 +0800, Len Brown wrote:
> 
> $ git bisect bad
> 7a55a3d54bd8d9e712e70cf9491f649e7e472a22 is first bad commit
> commit 7a55a3d54bd8d9e712e70cf9491f649e7e472a22
> Author: Bob Moore <robert.moore@intel.com>
> Date:   Thu Nov 13 11:08:59 2008 +0800
> 
>     ACPICA: Add Buffer->String conversion for predefined methods
>     
>     For predefined methods (such as _BIF), add automatic conversion for
>     objects that are required to be a String, but a Buffer was found
>     instead. This can happen when reading string battery data from
>     an operation region, because it used to be difficult to convert
>     the data from buffer to string from within the ASL. Linux BZ 11822.
>     
>     http://bugzilla.kernel.org/show_bug.cgi?id=11822
> 

Thanks, I'm looking at this.

Lin Ming


  reply	other threads:[~2008-11-13  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13  5:59 ACPICA Release 20081031 linuxized patch set Lin Ming
2008-11-13  6:13 ` Lin Ming
2008-11-13  6:54   ` Len Brown
2008-11-13  7:13     ` Lin Ming
2008-11-13  7:31     ` Len Brown
2008-11-13  7:54       ` Lin Ming [this message]
2008-11-13  9:37     ` Lin Ming
2008-11-13 22:05       ` Moore, Robert
     [not found]         ` <1226624335.30025.193.camel@minggr.sh.intel.com>
2008-11-27  7:13           ` 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=1226562896.30025.176.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=acpi@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=robert.moore@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