From: Aaron Lu <aaron.lu@amd.com>
To: Borislav Petkov <borislav.petkov@amd.com>,
Lin Ming <minggr@gmail.com>, Len Brown <lenb@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, Aaron Lu <aaron.lwe@gmail.com>,
Aaron Lu <aaron.lu@amd.com>, <stable@vger.kernel.org>,
<3.5+@domain.invalid>
Subject: [PATCH] ACPI: power: Use KERN_DEBUG when no power resources are found
Date: Fri, 10 Aug 2012 10:05:53 +0800 [thread overview]
Message-ID: <1344564353-493-1-git-send-email-aaron.lu@amd.com> (raw)
commit a606dac368eed5696fb38e16b1394f1d049c09e9 adds support to link
devices which have _PRx, if a device does not have _PRx, a warning
message will be printed.
This commit is for ZPODD on Intel's platform, on AMD's platform, there
is no _PRx to support ZPODD, we use _PSx.
So instead of printing a useless warning message on AMD's platform,
changing the print level to DEBUG to suppress this message.
Reported-by: Borislav Petkov <borislav.petkov@amd.com>
Cc: <stable@vger.kernel.org> 3.5+
Signed-off-by: Aaron Lu <aaron.lu@amd.com>
---
drivers/acpi/power.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
index 215ecd0..e5e01d9 100644
--- a/drivers/acpi/power.c
+++ b/drivers/acpi/power.c
@@ -460,7 +460,7 @@ int acpi_power_resource_register_device(struct device *dev, acpi_handle handle)
return ret;
no_power_resource:
- printk(KERN_WARNING PREFIX "Invalid Power Resource to register!");
+ printk(KERN_DEBUG PREFIX "Invalid Power Resource to register!");
return -ENODEV;
}
EXPORT_SYMBOL_GPL(acpi_power_resource_register_device);
--
1.7.11.3
next reply other threads:[~2012-08-10 2:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 2:05 Aaron Lu [this message]
2012-08-23 13:26 ` [PATCH] ACPI: power: Use KERN_DEBUG when no power resources are found Borislav Petkov
2012-08-24 22:36 ` Joe Perches
2012-08-29 2:01 ` Aaron Lu
2012-09-13 13:48 ` Borislav Petkov
2012-09-13 21:17 ` Rafael J. Wysocki
2012-09-13 22:10 ` Borislav Petkov
2012-09-13 22:27 ` Rafael J. Wysocki
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=1344564353-493-1-git-send-email-aaron.lu@amd.com \
--to=aaron.lu@amd.com \
--cc=3.5+@domain.invalid \
--cc=aaron.lwe@gmail.com \
--cc=borislav.petkov@amd.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minggr@gmail.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).