From: "Yu, Luming" <luming.yu@intel.com>
To: "Alex Williamson" <alex.williamson@hp.com>,
<linux-kernel@vger.kernel.org>,
<acpi-devel@lists.sourceforge.net>
Cc: "Brown, Len" <len.brown@intel.com>
Subject: RE: [ACPI] [PATCH] 2.4/2.6 use xdsdt to print table header
Date: Tue, 13 Jan 2004 15:38:38 +0800 [thread overview]
Message-ID: <3ACA40606221794F80A5670F0AF15F8401720CC2@PDSMSX403.ccr.corp.intel.com> (raw)
> I'm resending this patch to get it into the main ACPI source. This
> fixes a problem where the DSDT pointer in the FADT is NULL because it
> uses the 64bit XDSDT instead. The current code is happy to map a NULL
> address and return success to the caller. This can crash the
> system or
> printout garbage headers to the console. It's a simple
> matter to check
> table revision and use the XDSDT in favor of the DSDT. This has been
> living happily in both the 2.4 and 2.6 ia64 tree for some
> time. Please
> accept. Thanks,
I just checked with http://lia64.bkbits.net:8080/linux-ia64-2.4 .
The patch has been merged. Please take a look at
http://lia64.bkbits.net:8080/linux-ia64-2.4/diffs/drivers/acpi/tables.c@
1.11.1.1?nav=index.html|src/.|src/drivers|src/drivers/acpi|hist/drivers/
acpi/tables.c
and
http://lia64.bkbits.net:8080/linux-ia64-2.4/diffs/drivers/acpi/tables.c@
1.11.1.2?nav=index.html|src/.|src/drivers|src/drivers/acpi|hist/drivers/
acpi/tables.c
next reply other threads:[~2004-01-13 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 7:38 Yu, Luming [this message]
2004-01-13 15:28 ` [ACPI] [PATCH] 2.4/2.6 use xdsdt to print table header Alex Williamson
2004-01-18 2:41 Yu, Luming
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=3ACA40606221794F80A5670F0AF15F8401720CC2@PDSMSX403.ccr.corp.intel.com \
--to=luming.yu@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).