From: domen@coderock.org
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net, domen@coderock.org,
james4765@cwazy.co.uk, james4765@gmail.com
Subject: [patch 8/9] tridentfb: Clean up printk()'s in drivers/video/tridentfb.c
Date: Sun, 06 Mar 2005 11:36:34 +0100 [thread overview]
Message-ID: <20050306103634.BE6C51F23F@trashy.coderock.org> (raw)
This patch adds KERN_ constants to all of the printk()'s that need them in
drivers/video/tridentfb.c - resent after correcting one improper KERN_ constant.
Signed-off-by: James Nelson <james4765@gmail.com>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/drivers/video/tridentfb.c | 2 +-
kj-domen/include/video/trident.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -puN drivers/video/tridentfb.c~printk-drivers_video_tridentfb drivers/video/tridentfb.c
--- kj/drivers/video/tridentfb.c~printk-drivers_video_tridentfb 2005-03-05 16:13:03.000000000 +0100
+++ kj-domen/drivers/video/tridentfb.c 2005-03-05 16:13:03.000000000 +0100
@@ -1163,7 +1163,7 @@ static int __devinit trident_pci_probe(s
fb_info.var = default_var;
fb_info.device = &dev->dev;
if (register_framebuffer(&fb_info) < 0) {
- output("Could not register Trident framebuffer\n");
+ printk(KERN_ERR "tridentfb: could not register Trident framebuffer\n");
return -EINVAL;
}
output("fb%d: %s frame buffer device %dx%d-%dbpp\n",
diff -puN include/video/trident.h~printk-drivers_video_tridentfb include/video/trident.h
--- kj/include/video/trident.h~printk-drivers_video_tridentfb 2005-03-05 16:13:03.000000000 +0100
+++ kj-domen/include/video/trident.h 2005-03-05 16:13:03.000000000 +0100
@@ -9,7 +9,7 @@
#define debug(f,a...)
#endif
-#define output(f, a...) printk("tridentfb: " f, ## a)
+#define output(f, a...) pr_info("tridentfb: " f, ## a)
#define Kb (1024)
#define Mb (Kb*Kb)
_
-------------------------------------------------------
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-03-06 10:36 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=20050306103634.BE6C51F23F@trashy.coderock.org \
--to=domen@coderock.org \
--cc=adaplas@pol.net \
--cc=james4765@cwazy.co.uk \
--cc=james4765@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).