From: domen@coderock.org
To: dmo@osdl.org
Cc: linux-kernel@vger.kernel.org, domen@coderock.org, clucas@rotomalug.org
Subject: [patch 1/1] printk : drivers/block/DAC960.c
Date: Fri, 08 Apr 2005 09:51:50 +0200 [thread overview]
Message-ID: <20050408075151.775901F39A@trashy.coderock.org> (raw)
printk() calls should include appropriate KERN_* constant.
Signed-off-by: Christophe Lucas <clucas@rotomalug.org>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/drivers/block/DAC960.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -puN drivers/block/DAC960.c~printk-drivers_block_DAC960 drivers/block/DAC960.c
--- kj/drivers/block/DAC960.c~printk-drivers_block_DAC960 2005-04-05 12:57:58.000000000 +0200
+++ kj-domen/drivers/block/DAC960.c 2005-04-05 12:57:58.000000000 +0200
@@ -2496,7 +2496,7 @@ static boolean DAC960_RegisterBlockDevic
/* for now, let all request queues share controller's lock */
RequestQueue = blk_init_queue(DAC960_RequestFunction,&Controller->queue_lock);
if (!RequestQueue) {
- printk("DAC960: failure to allocate request queue\n");
+ printk(KERN_WARNING "DAC960: failure to allocate request queue\n");
continue;
}
Controller->RequestQueue[n] = RequestQueue;
@@ -3534,7 +3534,7 @@ static void DAC960_V1_ProcessCompletedCo
#ifdef FORCE_RETRY_FAILURE_DEBUG
if (!(++retry_count % 10000)) {
- printk("V1 error retry failure test\n");
+ printk(KERN_DEBUG "V1 error retry failure test\n");
normal_completion = false;
DAC960_V1_ReadWriteError(Command);
}
@@ -4622,7 +4622,7 @@ static void DAC960_V2_ProcessCompletedCo
#ifdef FORCE_RETRY_FAILURE_DEBUG
if (!(++retry_count % 10000)) {
- printk("V2 error retry failure test\n");
+ printk(KERN_DEBUG "V2 error retry failure test\n");
normal_completion = false;
DAC960_V2_ReadWriteError(Command);
}
_
reply other threads:[~2005-04-08 8:00 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=20050408075151.775901F39A@trashy.coderock.org \
--to=domen@coderock.org \
--cc=clucas@rotomalug.org \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.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