public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] acpi: make message more descriptive/meaningful
@ 2006-02-07  3:29 Randy.Dunlap
  2006-02-07 18:18 ` Patrick Mochel
  0 siblings, 1 reply; 4+ messages in thread
From: Randy.Dunlap @ 2006-02-07  3:29 UTC (permalink / raw)
  To: linux-acpi; +Cc: len.brown

[resend]

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 |    3 ++-
 1 files changed, 2 insertions(+), 1 deletion(-)

--- linux-2615-rc6g4.orig/drivers/acpi/bus.c
+++ linux-2615-rc6g4/drivers/acpi/bus.c
@@ -198,7 +198,8 @@ int acpi_bus_set_power(acpi_handle handl
 
 	if (!device->flags.power_manageable) {
 		ACPI_DEBUG_PRINT((ACPI_DB_WARN,
-				  "Device is not power manageable\n"));
+				  "Device '%s' is not power manageable\n",
+					device->kobj.name));
 		return_VALUE(-ENODEV);
 	}
 	/*


---

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] acpi: make message more descriptive/meaningful
  2006-02-07 18:18 ` Patrick Mochel
@ 2006-02-07 18:18   ` Randy.Dunlap
  2006-02-09 18:30     ` Thomas Renninger
  0 siblings, 1 reply; 4+ messages in thread
From: Randy.Dunlap @ 2006-02-07 18:18 UTC (permalink / raw)
  To: Patrick Mochel; +Cc: Randy.Dunlap, linux-acpi, len.brown

On Tue, 7 Feb 2006, Patrick Mochel wrote:

> On Mon, Feb 06, 2006 at 07:29:10PM -0800, Randy.Dunlap wrote:
>
> > Identify which device is not power-manageable to make
> > the message more useful.
>
>
> > --- linux-2615-rc6g4.orig/drivers/acpi/bus.c
> > +++ linux-2615-rc6g4/drivers/acpi/bus.c
> > @@ -198,7 +198,8 @@ int acpi_bus_set_power(acpi_handle handl
> >
> >  	if (!device->flags.power_manageable) {
> >  		ACPI_DEBUG_PRINT((ACPI_DB_WARN,
> > -				  "Device is not power manageable\n"));
> > +				  "Device '%s' is not power manageable\n",
> > +					device->kobj.name));
>
>
> This is good information, but does it have to come in such a scary message?
> It appears that something is wrong with the device, when in fact, it just
> doesn't support an optional capability.
>
> Could we demote the message to e.g. ACPI_DB_INFO?

Sure, fine with me.

-- 
~Randy

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] acpi: make message more descriptive/meaningful
  2006-02-07  3:29 [PATCH] acpi: make message more descriptive/meaningful Randy.Dunlap
@ 2006-02-07 18:18 ` Patrick Mochel
  2006-02-07 18:18   ` Randy.Dunlap
  0 siblings, 1 reply; 4+ messages in thread
From: Patrick Mochel @ 2006-02-07 18:18 UTC (permalink / raw)
  To: Randy.Dunlap; +Cc: linux-acpi, len.brown

On Mon, Feb 06, 2006 at 07:29:10PM -0800, Randy.Dunlap wrote:

> Identify which device is not power-manageable to make
> the message more useful.


> --- linux-2615-rc6g4.orig/drivers/acpi/bus.c
> +++ linux-2615-rc6g4/drivers/acpi/bus.c
> @@ -198,7 +198,8 @@ int acpi_bus_set_power(acpi_handle handl
>  
>  	if (!device->flags.power_manageable) {
>  		ACPI_DEBUG_PRINT((ACPI_DB_WARN,
> -				  "Device is not power manageable\n"));
> +				  "Device '%s' is not power manageable\n",
> +					device->kobj.name));


This is good information, but does it have to come in such a scary message?
It appears that something is wrong with the device, when in fact, it just
doesn't support an optional capability.

Could we demote the message to e.g. ACPI_DB_INFO? 

Thanks,


	Patrick

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] acpi: make message more descriptive/meaningful
  2006-02-07 18:18   ` Randy.Dunlap
@ 2006-02-09 18:30     ` Thomas Renninger
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Renninger @ 2006-02-09 18:30 UTC (permalink / raw)
  To: Randy.Dunlap; +Cc: Patrick Mochel, linux-acpi, len.brown

Randy.Dunlap wrote:
> On Tue, 7 Feb 2006, Patrick Mochel wrote:
> 
>> On Mon, Feb 06, 2006 at 07:29:10PM -0800, Randy.Dunlap wrote:
>>
>>> Identify which device is not power-manageable to make
>>> the message more useful.
>>
>>> --- linux-2615-rc6g4.orig/drivers/acpi/bus.c
>>> +++ linux-2615-rc6g4/drivers/acpi/bus.c
>>> @@ -198,7 +198,8 @@ int acpi_bus_set_power(acpi_handle handl
>>>
>>>  	if (!device->flags.power_manageable) {
>>>  		ACPI_DEBUG_PRINT((ACPI_DB_WARN,
>>> -				  "Device is not power manageable\n"));
>>> +				  "Device '%s' is not power manageable\n",
>>> +					device->kobj.name));
>>
>> This is good information, but does it have to come in such a scary message?
>> It appears that something is wrong with the device, when in fact, it just
>> doesn't support an optional capability.
>>
>> Could we demote the message to e.g. ACPI_DB_INFO?
> 
I already moved this one with the big debug to error/warn ... patch.
It should now be ACPI_DB_INFO, but I did not add the device name though...

   Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-02-09 18:30 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-07  3:29 [PATCH] acpi: make message more descriptive/meaningful Randy.Dunlap
2006-02-07 18:18 ` Patrick Mochel
2006-02-07 18:18   ` Randy.Dunlap
2006-02-09 18:30     ` Thomas Renninger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox