From: Len Brown <len.brown@intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: [BK PATCH] ACPI 2.6
Date: 29 Oct 2003 02:59:05 -0500 [thread overview]
Message-ID: <1067414344.15257.5.camel@dhcppc4> (raw)
Hi Linus, please do a
bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.6.0
These two csets undo recent changes that caused crashes.
thanks,
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.0-test9/acpi-20031002-2.6.0-test9.diff.gz
This will update the following files:
drivers/acpi/dispatcher/dsopcode.c | 8 +++-----
drivers/acpi/ec.c | 16 ++--------------
2 files changed, 5 insertions(+), 19 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (03/10/28 1.1373)
[ACPI] REVERT ACPICA-20030918 CONFIG_ACPI_DEBUG printk that caused
crash
http://bugzilla.kernel.org/show_bug.cgi?id=1341
<len.brown@intel.com> (03/10/28 1.1372)
[ACPI] REVERT acpi_ec_gpe_query(ec) fix that crashed non-T40 boxes
http://bugme.osdl.org/show_bug.cgi?id=1171
reply other threads:[~2003-10-29 7:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1067414344.15257.5.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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