public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Lin Ming <minggr@gmail.com>
Cc: Lin Ming <ming.m.lin@intel.com>,
	"Moore, Robert" <robert.moore@intel.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: ACPICA release 20110413 linuxized patches
Date: Mon, 25 Apr 2011 16:50:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.02.1104251648590.26994@x980> (raw)
In-Reply-To: <BANLkTik4NAmL+tJaecQ4pdmrpPZG8fw=Lw@mail.gmail.com>

On Mon, 25 Apr 2011, Lin Ming wrote:

> On Fri, Apr 15, 2011 at 9:10 AM, Lin Ming <ming.m.lin@intel.com> wrote:
> > Hi, Len
> >
> > ACPICA release 20110413 linuxized patches attached.
> > Build and tested on my notebook without problem.
> >
> > [PATCH 1/6] ACPICA: Split all internal Global Lock functions to new file - evglock
> > [PATCH 2/6] ACPICA: Add more methods eligible for NULL package element removal
> > [PATCH 3/6] ACPICA: Update internal address SpaceID for DataTable regions
> > [PATCH 4/6] ACPICA: Move ACPI_NUM_PREDEFINED_REGIONS to a more appropriate place
> > [PATCH 5/6] ACPICA: Execute an orphan _REG method under the EC device
> > [PATCH 6/6] ACPICA: Update to version 20110413
> 
> Hi, Len
> 
> Have you applied this?

No, I've been out of town since the 15th when you sent it (I'm back now).

The acpica branch currently has this:

Lin Ming (3):
      ACPI: osl, add acpi_os_create_lock interface
      ACPICA: Use acpi_os_create_lock interface
      ACPICA: Fix code divergence of global lock handling

cheers,
-Len


      reply	other threads:[~2011-04-25 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  1:10 ACPICA release 20110413 linuxized patches Lin Ming
2011-04-25  5:22 ` Lin Ming
2011-04-25 20:50   ` Len Brown [this message]

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=alpine.LFD.2.02.1104251648590.26994@x980 \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=minggr@gmail.com \
    --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