linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [BK PATCH] ACPI 2.4
Date: 29 Oct 2003 03:09:14 -0500	[thread overview]
Message-ID: <1067414953.15257.17.camel@dhcppc4> (raw)

Hi Marcelo, please do a 

	bk pull http://linux-acpi.bkbits.net/linux-acpi-release-2.4.23

	This request includes the earlier x86_64 ACPI build fix,
	plus fixes two crash regressions due to recent deltas,
	plus picks up Andrew Morton's tweak to printk from 2.6.

thanks,
-Len

ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.4.23-pre8/acpi-20031002-2.4.23-pre8.diff.gz

This will update the following files:
 arch/x86_64/kernel/acpi.c          |   29 ++++++++++++++++++++++++-
 drivers/acpi/dispatcher/dsopcode.c |    8 ++----
 drivers/acpi/ec.c                  |   16 +------------
 lib/vsprintf.c                     |    3 +-
 4 files changed, 35 insertions(+), 21 deletions(-)

through these ChangeSets:

<akpm@osdl.org> (03/10/28 1.1063.44.35)
   [PATCH] make printk more robust with "null" pointers
   
   Expand printk's traditional handling of null pointers so that
anything in the
   first page is considered a null pointer.
   
   This gives us better behaviour when someone (acpi..) accidentally
prints a
   string which is embedded in a struct, the pointer to which is null.

<len.brown@intel.com> (03/10/28 1.1063.44.34)
   [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.1063.44.33)
   [ACPI] REVERT acpi_ec_gpe_query(ec) T40 fix that crashed other boxes
   http://bugme.osdl.org/show_bug.cgi?id=1171

<len.brown@intel.com> (03/10/28 1.1063.44.32)
   [ACPI] fix x86_64 build (Jeff Garzik)






                 reply	other threads:[~2003-10-29  8:09 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=1067414953.15257.17.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;
as well as URLs for NNTP newsgroup(s).