From: domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org
To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org,
clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org
Subject: [patch 1/2] printk : drivers/block/drivers/acpi/container.c
Date: Fri, 08 Apr 2005 09:50:31 +0200 [thread overview]
Message-ID: <20050408075031.E91851EE91@trashy.coderock.org> (raw)
printk() calls should include appropriate KERN_* constant.
Signed-off-by: Christophe Lucas <clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org>
Signed-off-by: Domen Puncer <domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org>
---
kj-domen/drivers/acpi/container.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/acpi/container.c~printk-drivers_acpi_container drivers/acpi/container.c
--- kj/drivers/acpi/container.c~printk-drivers_acpi_container 2005-04-05 12:57:57.000000000 +0200
+++ kj-domen/drivers/acpi/container.c 2005-04-05 12:57:57.000000000 +0200
@@ -174,7 +174,7 @@ container_notify_cb(acpi_handle handle,
case ACPI_NOTIFY_BUS_CHECK:
/* Fall through */
case ACPI_NOTIFY_DEVICE_CHECK:
- printk("Container driver received %s event\n",
+ printk(KERN_INFO "Container driver received %s event\n",
(type == ACPI_NOTIFY_BUS_CHECK)?
"ACPI_NOTIFY_BUS_CHECK":"ACPI_NOTIFY_DEVICE_CHECK");
status = acpi_bus_get_device(handle, &device);
_
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
reply other threads:[~2005-04-08 7:50 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=20050408075031.E91851EE91@trashy.coderock.org \
--to=domen-cvscvcplwozg9huczpvpmw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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