From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: [BKPATCH] ACPI for 2.4
Date: 25 Feb 2004 05:01:05 -0500 [thread overview]
Message-ID: <1077700687.5912.188.camel@dhcppc4> (raw)
Hi Marcelo, please do a
bk pull bk://linux-acpi.bkbits.net/linux-acpi-release-2.4.26
thanks,
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.4.25/acpi-20040211-2.4.25.diff.gz
This will update the following files:
drivers/acpi/Config.in | 3 --
drivers/acpi/dispatcher/dsmthdat.c | 9 ++++--
drivers/acpi/dispatcher/dsobject.c | 5 +++
drivers/acpi/dispatcher/dsopcode.c | 6 ++--
drivers/acpi/dispatcher/dsutils.c | 3 +-
drivers/acpi/dispatcher/dswstate.c | 2 -
drivers/acpi/executer/exconvrt.c | 35 ++++++++++++++++---------
drivers/acpi/executer/exfldio.c | 4 +-
drivers/acpi/executer/exmisc.c | 8 +++--
drivers/acpi/executer/exoparg2.c | 4 ++
drivers/acpi/executer/exprep.c | 2 -
drivers/acpi/executer/exresolv.c | 6 ++--
drivers/acpi/executer/exresop.c | 4 +-
drivers/acpi/executer/exstore.c | 29 ++++++++++++++------
drivers/acpi/executer/exstoren.c | 8 +++++
drivers/acpi/namespace/nsaccess.c | 2 -
drivers/acpi/parser/psargs.c | 4 +-
include/acpi/acconfig.h | 2 -
18 files changed, 87 insertions(+), 49 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (04/02/13 1.1063.46.74)
[ACPI] ACPICA 20040211 udpate from Bob Moore
Completed investigation and implementation of the
call-by-reference mechanism for control method arguments.
Fixed a problem where a store of an object into an indexed
package could fail if the store occurs within a different
method than the method that created the package.
Fixed a problem where the ToDecimal operator could return
incorrect results.
Fixed a problem where the CopyObject operator could fail
on some of the more obscure objects (e.g., Reference objects.)
Improved the output of the Debug object to display buffer,
package, and index objects.
Fixed a problem where constructs of the form "RefOf (ArgX)"
did not return the expected result.
Added permanent ACPI_REPORT_ERROR macros for all instances of the
ACPI_AML_INTERNAL exception.
<len.brown@intel.com> (04/02/13 1.1063.46.73)
[ACPI] revert previous AML param patch for ACPICA update
<len.brown@intel.com> (04/02/10 1.1063.46.72)
[ACPI] CONFIG_ACPI_NUMA depends on CONFIG_IA64
next reply other threads:[~2004-02-25 10:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 10:01 Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 8:32 [BKPATCH] ACPI for 2.4 Len Brown
2004-11-23 6:34 Len Brown
2004-11-16 19:26 Len Brown
2004-11-09 8:17 Len Brown
2004-10-28 9:33 Len Brown
2004-06-18 7:32 Len Brown
2004-05-20 6:14 Len Brown
2004-05-06 22:28 Len Brown
2004-04-01 12:24 O.Sezer
2004-04-01 12:57 ` O.Sezer
2004-04-01 10:40 Len Brown
2004-03-27 0:53 Len Brown
2004-03-23 10:43 Len Brown
2004-03-14 6:01 Len Brown
2004-03-06 6:32 Len Brown
2004-02-07 9:10 Len Brown
2004-02-08 8:20 ` Willy Tarreau
2004-02-08 9:08 ` Willy Tarreau
2003-11-18 20:58 Len Brown
2003-11-20 11:16 ` Len Brown
2003-11-21 17:49 ` Willy Tarreau
2003-11-21 18:46 ` Willy Tarreau
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=1077700687.5912.188.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
/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