From: Thomas Renninger <trenn@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@vger.kernel.org, rdunlap@xenotime.net
Subject: Re: "Device is not power manageable"
Date: Wed, 22 Feb 2006 12:44:41 +0100 [thread overview]
Message-ID: <200602221244.42339.trenn@suse.de> (raw)
In-Reply-To: <20060221190840.5e67d07e.akpm@osdl.org>
On Wednesday 22 February 2006 04:08, you wrote:
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> >
> > Here's the patch that I have used.
> >
> > --
> >
> > From: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>
> >
> > Identify which device is not power-manageable to make
> > the message more useful.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> > ---
> > drivers/acpi/bus.c | 5 +++--
> > 1 files changed, 3 insertions(+), 2 deletions(-)
> >
> > --- linux-2616-rc4.orig/drivers/acpi/bus.c
> > +++ linux-2616-rc4/drivers/acpi/bus.c
> > @@ -197,8 +197,9 @@ int acpi_bus_set_power(acpi_handle handl
> > /* Make sure this is a valid target state */
> >
> > if (!device->flags.power_manageable) {
> > - ACPI_DEBUG_PRINT((ACPI_DB_WARN,
> > - "Device is not power manageable\n"));
> > + ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> > + "Device '%s' is not power manageable\n",
> > + device->kobj.name));
> > return_VALUE(-ENODEV);
> > }
> > /*
>
> Thanks. I guess that won't be very popular due to using linux-specific
> stuff in a generic file, but I'll merge it.
That will conflict with latest patches:
ACPI_DEBUG_PRINT((ACPI_DB_WARN, ...)) have been converted to
ACPI_WARNING((AE_INFO, ...)).
This was done because a lot real error/warning messages were only printed with
ACPI_DEBUG=y (like all ACPI_DEBUG_PRINT messages).
In this case I used ACPI_INFO((AE_INFO,...)) as I knew the message
pops up here and there.
This one lets the message vanish totally and only shows it with ACPI_DEBUG=y and
acpi_dbg_level | ACPI_DEBUG_INFO:
signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
signed-off-by: Thomas Renninger <trenn@suse.de>
bus.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletion(-)
Index: linux-2.6.15/drivers/acpi/bus.c
===================================================================
--- linux-2.6.15.orig/drivers/acpi/bus.c
+++ linux-2.6.15/drivers/acpi/bus.c
@@ -196,7 +196,9 @@ int acpi_bus_set_power(acpi_handle handl
/* Make sure this is a valid target state */
if (!device->flags.power_manageable) {
- ACPI_INFO((AE_INFO, "Device is not power manageable"));
+ ACPI_DEBUG_PRINT((ACPI_DB_INFO,
+ "Device %s is not power manageable",
+ device->kobj.name));
return_VALUE(-ENODEV);
}
/*
prev parent reply other threads:[~2006-02-22 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 12:27 "Device is not power manageable" Andrew Morton
2006-02-21 15:41 ` Randy.Dunlap
2006-02-22 2:59 ` Randy.Dunlap
2006-02-22 3:08 ` Andrew Morton
2006-02-22 11:44 ` Thomas Renninger [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=200602221244.42339.trenn@suse.de \
--to=trenn@suse.de \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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