From: Andi Kleen <ak@linux.intel.com>
To: Lin Ming <ming.m.lin@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: [PATCH] acpi: replace AE_BAD_ADDRESS exception code with AE_ERROR
Date: Mon, 11 Aug 2008 13:26:06 +0200 [thread overview]
Message-ID: <48A021CE.9040706@linux.intel.com> (raw)
In-Reply-To: <1218167831.4978.11.camel@minggr.sh.intel.com>
Lin Ming wrote:
> Hi, Andi
>
> The AE_BAD_ADDRESS exception code is now unused in ACPICA.
> For linux, it's only used at wmi.c and acer-wmi.c.
> I checked both wmi.c and acer-wmi.c, the AE_BAD_ADDRESS exception code
> has no special meaning. The parent functions just call AE_SUCCESS() or
> AE_FAILURE() to check the return status.
> So it's safe to replace AE_BAD_ADDRESS with AE_ERROR.
Queued for test thanks
-Andi
prev parent reply other threads:[~2008-08-11 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 3:57 [PATCH] acpi: replace AE_BAD_ADDRESS exception code with AE_ERROR Lin Ming
2008-08-08 4:00 ` Moore, Robert
2008-08-08 4:03 ` Lin Ming
2008-08-08 21:14 ` Carlos Corbacho
2008-08-11 11:26 ` Andi Kleen [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=48A021CE.9040706@linux.intel.com \
--to=ak@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
/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