From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Lv Zheng <zetalog@gmail.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH 1/6] ACPICA: Hardware: Reduce divergences for sleep functions.
Date: Thu, 29 May 2014 12:24:55 +0200 [thread overview]
Message-ID: <20140529102455.GA18151@ugly.fritz.box> (raw)
In-Reply-To: <f8980f7d9788d609314a8ac5b6b4b1ef4a39bd89.1401210685.git.lv.zheng@intel.com>
series confirmed to work on top of linux-pm-next.
On Wed, May 28, 2014 at 01:27:37AM +0800, Lv Zheng wrote:
> From: Lv Zheng <lv.zheng@intel.com>
>
> This patch is generated to reduce source code differences between Linux and
> ACPICA so that further sleep related modifications can be applied directly
> without human interventions. Lv Zheng.
>
> Signed-off-by: Lv Zheng <lv.zheng@intel.com>
> Cc: Oswald Buddenhagen <ossi@kde.org>
> ---
> drivers/acpi/acpica/hwxfsleep.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/acpi/acpica/hwxfsleep.c b/drivers/acpi/acpica/hwxfsleep.c
> index 6921c7f..103d9a7 100644
> --- a/drivers/acpi/acpica/hwxfsleep.c
> +++ b/drivers/acpi/acpica/hwxfsleep.c
> @@ -138,7 +138,6 @@ acpi_status acpi_set_firmware_waking_vector64(u64 physical_address)
> {
> ACPI_FUNCTION_TRACE(acpi_set_firmware_waking_vector64);
>
> -
> /* Determine if the 64-bit vector actually exists */
>
> if ((acpi_gbl_FACS->length <= 32) || (acpi_gbl_FACS->version < 1)) {
> @@ -154,7 +153,6 @@ acpi_status acpi_set_firmware_waking_vector64(u64 physical_address)
>
> ACPI_EXPORT_SYMBOL(acpi_set_firmware_waking_vector64)
> #endif
> -
> /*******************************************************************************
> *
> * FUNCTION: acpi_enter_sleep_state_s4bios
> --
> 1.7.10
>
>
next prev parent reply other threads:[~2014-05-29 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 0:11 [PATCH] ACPICA: Revert "ACPICA: Add option to favor 32-bit FADT addresses." Rafael J. Wysocki
2014-05-12 1:10 ` Zheng, Lv
2014-05-12 8:51 ` Zheng, Lv
2014-05-13 0:09 ` Rafael J. Wysocki
2014-05-13 1:05 ` Zheng, Lv
2014-05-13 1:30 ` Rafael J. Wysocki
2014-05-13 4:54 ` Zheng, Lv
2014-05-13 8:50 ` [PATCH] Tables: Restore old behavor to favor 32-bit FADT addresses Lv Zheng
2014-05-26 13:06 ` Rafael J. Wysocki
2014-05-27 17:27 ` [RFC PATCH 0/6] ACPICA: 64bit FADT addresses enabling Lv Zheng
2014-05-27 17:27 ` [RFC PATCH 1/6] ACPICA: Hardware: Reduce divergences for sleep functions Lv Zheng
2014-05-29 10:24 ` Oswald Buddenhagen [this message]
2014-05-30 2:15 ` Zheng, Lv
2014-05-27 17:27 ` [RFC PATCH 2/6] ACPICA: Hardware: Enable 64-bit firmware waking vector for selected FACS Lv Zheng
2014-05-27 17:28 ` [RFC PATCH 3/6] ACPI: sleep: Update acpi_set_firmware_waking_vector() invocations to favor 32-bit firmware waking vector Lv Zheng
2014-05-27 17:28 ` [RFC PATCH 4/6] ACPICA: Tables: Enable both 32-bit and 64-bit FACS Lv Zheng
2014-05-27 17:28 ` [RFC PATCH 5/6] ACPICA: Hardware: Enable firmware waking vector for " Lv Zheng
2014-05-27 17:29 ` [RFC PATCH 6/6] ACPICA: Tables: Enable default 64-bit FADT addresses favor Lv Zheng
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=20140529102455.GA18151@ugly.fritz.box \
--to=oswald.buddenhagen@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=zetalog@gmail.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;
as well as URLs for NNTP newsgroup(s).