From: Prarit Bhargava <prarit@redhat.com>
To: "Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"devel@acpica.org" <devel@acpica.org>
Cc: "Zheng, Lv" <lv.zheng@intel.com>, Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Box, David E" <david.e.box@intel.com>
Subject: Re: [PATCH] ACPICA: AcpiGetSleepTypeData: Failure to find \_Sx should not result in a loud warning
Date: Wed, 07 Oct 2015 11:57:27 -0400 [thread overview]
Message-ID: <561540E7.30809@redhat.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E37D362FF7@ORSMSX112.amr.corp.intel.com>
On 10/07/2015 11:52 AM, Moore, Robert wrote:
> It would be easy to remove (or partially remove) the warning. Hopefully the calling code will handle AE_NOT_FOUND correctly.
>
In the specific case of the \_Sx sleep states the code does handle the
AE_NOT_FOUND correctly. The issue is solely the warning being displayed when
there should be no warning.
P.
next prev parent reply other threads:[~2015-10-07 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 17:28 [PATCH] ACPICA: AcpiGetSleepTypeData: Failure to find \_Sx should not result in a loud warning Prarit Bhargava
2015-10-01 17:57 ` Moore, Robert
2015-10-01 22:28 ` Rafael J. Wysocki
2015-10-07 15:28 ` Prarit Bhargava
2015-10-07 15:52 ` Moore, Robert
2015-10-07 15:57 ` Prarit Bhargava [this message]
2015-10-07 16:27 ` Moore, Robert
2015-10-07 18:50 ` [PATCH] ACPICA: AcpiGetSleepTypeData: Failure to find \_Sx should not result in a loud warning [v2] Prarit Bhargava
2015-10-08 14:19 ` Moore, Robert
2015-10-08 14:23 ` Prarit Bhargava
2015-10-09 2:02 ` Zheng, Lv
2015-10-09 5:26 ` Zheng, Lv
2015-10-09 11:29 ` Prarit Bhargava
2015-10-09 14:04 ` Moore, Robert
2015-10-10 1:22 ` Zheng, Lv
2015-10-10 1:37 ` Zheng, Lv
2015-10-13 20:59 ` Moore, Robert
2015-10-14 1:47 ` Zheng, Lv
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=561540E7.30809@redhat.com \
--to=prarit@redhat.com \
--cc=david.e.box@intel.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@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;
as well as URLs for NNTP newsgroup(s).