From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] 2.4/2.6 use xdsdt to print table header
Date: 26 Jan 2004 16:58:31 -0500 [thread overview]
Message-ID: <1075154310.2485.35.camel@dhcppc4> (raw)
In-Reply-To: <1073953935.6497.173.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
Accepted.
Thanks Alex,
-Len
On Mon, 2004-01-12 at 19:32, Alex Williamson wrote:
> 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,
>
> Alex
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-26 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 0:32 [PATCH] 2.4/2.6 use xdsdt to print table header Alex Williamson
[not found] ` <1073953935.6497.173.camel-Wmjt7DDUnIVxnVILBQAtiA@public.gmane.org>
2004-01-26 21:58 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 7:38 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720CC2-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13 15:28 ` 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=1075154310.2485.35.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=alex.williamson-VXdhtT5mjnY@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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