public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: robert.moore@intel.com
Cc: linux-acpi@vger.kernel.org
Subject: ACPICA vs. Linux status
Date: Tue, 29 May 2007 18:15:09 -0400	[thread overview]
Message-ID: <200705291815.09493.lenb@kernel.org> (raw)

> Subject: [Patch 1/8] ACPICA: Update _OSI string list

applied

> Subject: [Patch 2/8] ACPICA: Changes for Cygwin compatibility

applied

> Subject: [Patch 3/8] ACPICA: Support for external package objects as method arguments

applied after hand editing.
Unclear why hand-ending was necessary, as there were no Linux specific
changes to this file beneath this delta.
Must be either Lindent weirdness or 0x20070320, mentioned below.

> Subject: [Patch 4/8] ACPICA: Fixed possible corruption of global GPE list

applied

> Subject: [Patch 5/8] ACPICA: Fix for update of the Global Lock Handle

did not apply, as it conflicts with the pre-existing Linux fix here,
which I decided to keep for the time being.

> Subject: [Patch 6/8] ACPICA: Change to make Notify() operator completely synchronous

While the patch applied, it did not work, and is thus rejected.
It caused "cat temperature" on my nx6325 to deadlock someplace
in the region of a trip point.

> Subject: [Patch 7/8] ACPICA: Clear reserved fields for incoming ACPI 1.0 FADTs

applied.

> Subject: [Patch 8/8] ACPICA: Update version to 20070508

did not apply, and didn't hand-apply it for two reasons:
1. we don't yet include all the changes from 20070508.

2. It expects ACPICA version 0x20070320 underneath,
but Linux doesn't have that version, it is at 0x20070126.

Bob, Please send the patch series for 0x20070320.

thanks,
-Len

             reply	other threads:[~2007-05-29 22:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 22:15 Len Brown [this message]
2007-05-30  7:43 ` ACPICA vs. Linux status Alexey Starikovskiy
2007-05-30 15:56   ` 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=200705291815.09493.lenb@kernel.org \
    --to=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