All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Patrick Mochel <mochel@linux.intel.com>,
	linux-acpi@vger.kernel.org, len.brown@intel.com
Subject: Re: [PATCH] acpi: make message more descriptive/meaningful
Date: Thu, 09 Feb 2006 19:30:23 +0100	[thread overview]
Message-ID: <43EB8A3F.20303@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0602071017430.12589@shark.he.net>

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

      reply	other threads:[~2006-02-09 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=43EB8A3F.20303@suse.de \
    --to=trenn@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mochel@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.