From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Randy.Dunlap" <rddunlap-3NddpPZAyC0@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] correct ACPI URL
Date: 26 Jan 2004 14:49:08 -0500 [thread overview]
Message-ID: <1075146544.2485.0.camel@dhcppc4> (raw)
In-Reply-To: <20040125165934.1d89f8e7.rddunlap-3NddpPZAyC0@public.gmane.org>
Accepted
thanks,
-Len
On Sun, 2004-01-25 at 19:59, Randy.Dunlap wrote:
> Please apply to 2.6.current.
>
> --
> ~Randy
>
>
> description: use correct ACPI URL;
>
> diffstat:=
> arch/i386/boot/setup.S | 2 +-
> 1 files changed, 1 insertion(+), 1 deletion(-)
>
> diff -Naurp ./arch/i386/boot/setup.S~acpi_url ./arch/i386/boot/setup.S
> --- ./arch/i386/boot/setup.S~acpi_url 2004-01-08 22:59:44.000000000 -0800
> +++ ./arch/i386/boot/setup.S 2004-01-25 16:48:02.000000000 -0800
> @@ -307,7 +307,7 @@ loader_ok:
> # a whole bunch of different types, and allows memory holes and
> # everything. We scan through this memory map and build a list
> # of the first 32 memory areas, which we return at [E820MAP].
> -# This is documented at http://www.teleport.com/~acpi/acpihtml/topic245.htm
> +# This is documented at http://www.acpi.info/, in the ACPI 2.0 specification.
>
> #define SMAP 0x534d4150
>
-------------------------------------------------------
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
prev parent reply other threads:[~2004-01-26 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 0:59 [PATCH] correct ACPI URL Randy.Dunlap
[not found] ` <20040125165934.1d89f8e7.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-01-26 19:49 ` Len Brown [this message]
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=1075146544.2485.0.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rddunlap-3NddpPZAyC0@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