From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Len Brown <lenb@kernel.org>, Borislav Petkov <bp@amd64.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH RESEND] ACPI: power: Use KERN_DEBUG when no power resources are found
Date: Fri, 14 Sep 2012 21:30:25 +0200 [thread overview]
Message-ID: <201209142130.25635.rjw@sisk.pl> (raw)
In-Reply-To: <1347584884-1486-1-git-send-email-aaron.lu@intel.com>
On Friday, September 14, 2012, Aaron Lu wrote:
> 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 ZPODD capable platforms, on other
> platforms, it has no problem if there is no power resource for this
> device, so a warning here is not appropriate, change it to debug.
>
> Reported-by: Borislav Petkov <bp@amd64.org>
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
Applied to the linux-next branch of the linux-pm.git tree as a -stable fix
for v3.6.
Thanks,
Rafael
> ---
> 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);
>
prev parent reply other threads:[~2012-09-14 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 1:08 [PATCH RESEND] ACPI: power: Use KERN_DEBUG when no power resources are found Aaron Lu
2012-09-14 19:30 ` Rafael J. Wysocki [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=201209142130.25635.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=bp@amd64.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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).