From: Jesper Juhl <jesper.juhl@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Paul Diefenbaugh <paul.s.diefenbaugh@intel.com>,
Len Brown <len.brown@intel.com>,
linux-acpi@vger.kernel.org, akpm@osdl.org,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: [PATCH][TRIVIAL][ACPI] Missing newline in acpi messes up dmesg output
Date: Sun, 9 Jul 2006 00:43:26 +0200 [thread overview]
Message-ID: <200607090043.27121.jesper.juhl@gmail.com> (raw)
(This was already send once on July 6'th but got no response, so resending)
Hi,
There's a tiny bug in 2.6.18-rc1.
In drivers/acpi/bus.c::acpi_bus_set_power() there's a check to see if
the device is power_manageable and if not then print a debug message
and return -ENODEV. The debug printk() is missing a \n.
The printk statement looks like this :
printk(KERN_DEBUG "Device `[%s]' is not power manageable",
device->kobj.name);
As you can see, there's no newline at the end, and that causes
problems for the next message to be printed.
On my system the above results in this in dmesg :
...
Device `[PEB1]' is not power manageable<6>ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 29 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
Device `[PEB2]' is not power manageable<6>ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 34 (level, low) -> IRQ 17
...
Adding a newline (as the patch below does) turns this into
...
Device `[PEB1]' is not power manageable
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 29 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
Device `[PEB2]' is not power manageable
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 34 (level, low) -> IRQ 17
...
Which is much nicer :-)
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
drivers/acpi/bus.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.18-rc1-orig/drivers/acpi/bus.c 2006-07-06 19:39:29.000000000 +0200
+++ linux-2.6.18-rc1/drivers/acpi/bus.c 2006-07-06 23:23:12.000000000 +0200
@@ -192,7 +192,7 @@ int acpi_bus_set_power(acpi_handle handl
/* Make sure this is a valid target state */
if (!device->flags.power_manageable) {
- printk(KERN_DEBUG "Device `[%s]' is not power manageable",
+ printk(KERN_DEBUG "Device `[%s]' is not power manageable\n",
device->kobj.name);
return -ENODEV;
}
reply other threads:[~2006-07-08 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200607090043.27121.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.s.diefenbaugh@intel.com \
/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
Powered by JetHome