* Re: [PATCH 30/30 v2] Staging: comedi: fix printk() issue in das16m1.c
2011-07-18 9:44 ` [PATCH 30/30 v2] Staging: comedi: fix printk() issue in das16m1.c Ravishankar
@ 2011-07-18 9:43 ` Jesper Juhl
2011-07-18 15:46 ` Joe Perches
0 siblings, 1 reply; 3+ messages in thread
From: Jesper Juhl @ 2011-07-18 9:43 UTC (permalink / raw)
To: Ravishankar; +Cc: gregkh, wfp5p, devel, linux-kernel, Ravishankar
On Mon, 18 Jul 2011, Ravishankar wrote:
> From: Ravishankar <ravi.shankar@greenturtles.in>
>
> This is a patch to the das16m1.c file that fixes up a printk() warning found by the checkpatch.pl tool
>
> Signed-off-by: Ravishankar <ravishankarkm32@gmail.com>
> ---
>
> After understanding code I have changed 8 printk statement in int das16m1_attach function.
>
> drivers/staging/comedi/drivers/das16m1.c | 16 +++++++++-------
> 1 files changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/das16m1.c b/drivers/staging/comedi/drivers/das16m1.c
> index efc6132..d737ed2 100644
> --- a/drivers/staging/comedi/drivers/das16m1.c
> +++ b/drivers/staging/comedi/drivers/das16m1.c
> @@ -680,17 +680,19 @@ static int das16m1_attach(struct comedi_device *dev,
>
> dev->board_name = thisboard->name;
>
> - printk(" io 0x%lx-0x%lx 0x%lx-0x%lx",
> + printk(KERN_INFO " requesing the I/O region from 0x%lx-0x%lx 0x%lx-0x%lx",
Correct spelling is "requesting" and the "from" should either have a
matching "to" or just be dropped IMHO.
Personally I'd just make it:
" requesting I/O region 0x%lx-0x%lx 0x%lx-0x%lx"
> iobase, iobase + DAS16M1_SIZE,
> iobase + DAS16M1_82C55, iobase + DAS16M1_82C55 + DAS16M1_SIZE2);
> if (!request_region(iobase, DAS16M1_SIZE, driver_das16m1.driver_name)) {
> - printk(" I/O port conflict\n");
> - return -EIO;
> + printk(KERN_INFO "the IO REGION is busy, quitting\n");
> + return -EBUSY;
> }
> if (!request_region(iobase + DAS16M1_82C55, DAS16M1_SIZE2,
> driver_das16m1.driver_name)) {
> release_region(iobase, DAS16M1_SIZE);
> - printk(" I/O port conflict\n");
> + printk(KERN_INFO " releasing the I/O port region\n");
I think the original text was better.
--
Jesper Juhl <jj@chaosbits.net> http://www.chaosbits.net/
Don't top-post http://www.catb.org/jargon/html/T/top-post.html
Plain text mails only, please.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [PATCH 30/30 v2] Staging: comedi: fix printk() issue in das16m1.c
[not found] <[PATCH]Staging: comedi: fix printk() issue in das16m1.c>
@ 2011-07-18 9:44 ` Ravishankar
2011-07-18 9:43 ` Jesper Juhl
0 siblings, 1 reply; 3+ messages in thread
From: Ravishankar @ 2011-07-18 9:44 UTC (permalink / raw)
To: gregkh, wfp5p; +Cc: devel, linux-kernel, Ravishankar, Ravishankar
From: Ravishankar <ravi.shankar@greenturtles.in>
This is a patch to the das16m1.c file that fixes up a printk() warning found by the checkpatch.pl tool
Signed-off-by: Ravishankar <ravishankarkm32@gmail.com>
---
After understanding code I have changed 8 printk statement in int das16m1_attach function.
drivers/staging/comedi/drivers/das16m1.c | 16 +++++++++-------
1 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/comedi/drivers/das16m1.c b/drivers/staging/comedi/drivers/das16m1.c
index efc6132..d737ed2 100644
--- a/drivers/staging/comedi/drivers/das16m1.c
+++ b/drivers/staging/comedi/drivers/das16m1.c
@@ -680,17 +680,19 @@ static int das16m1_attach(struct comedi_device *dev,
dev->board_name = thisboard->name;
- printk(" io 0x%lx-0x%lx 0x%lx-0x%lx",
+ printk(KERN_INFO " requesing the I/O region from 0x%lx-0x%lx 0x%lx-0x%lx",
iobase, iobase + DAS16M1_SIZE,
iobase + DAS16M1_82C55, iobase + DAS16M1_82C55 + DAS16M1_SIZE2);
if (!request_region(iobase, DAS16M1_SIZE, driver_das16m1.driver_name)) {
- printk(" I/O port conflict\n");
- return -EIO;
+ printk(KERN_INFO "the IO REGION is busy, quitting\n");
+ return -EBUSY;
}
if (!request_region(iobase + DAS16M1_82C55, DAS16M1_SIZE2,
driver_das16m1.driver_name)) {
release_region(iobase, DAS16M1_SIZE);
- printk(" I/O port conflict\n");
+ printk(KERN_INFO " releasing the I/O port region\n");
return -EIO;
}
dev->iobase = iobase;
@@ -702,15 +704,15 @@ static int das16m1_attach(struct comedi_device *dev,
ret = request_irq(irq, das16m1_interrupt, 0,
driver_das16m1.driver_name, dev);
if (ret < 0) {
- printk(", irq unavailable\n");
+ printk(KERN_INFO ", irq unavailable\n");
return ret;
}
dev->irq = irq;
- printk(", irq %u\n", irq);
+ printk(KERN_INFO ", irq %u\n", irq);
} else if (irq == 0) {
- printk(", no irq\n");
+ printk(KERN_INFO ", no irq\n");
} else {
- printk(", invalid irq\n"
+ printk(KERN_ERR ", invalid irq\n"
" valid irqs are 2, 3, 5, 7, 10, 11, 12, or 15\n");
return -EINVAL;
}
--
1.6.5.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 30/30 v2] Staging: comedi: fix printk() issue in das16m1.c
2011-07-18 9:43 ` Jesper Juhl
@ 2011-07-18 15:46 ` Joe Perches
0 siblings, 0 replies; 3+ messages in thread
From: Joe Perches @ 2011-07-18 15:46 UTC (permalink / raw)
To: Jesper Juhl; +Cc: Ravishankar, devel, gregkh, linux-kernel, Ravishankar
On Mon, 2011-07-18 at 11:43 +0200, Jesper Juhl wrote:
> On Mon, 18 Jul 2011, Ravishankar wrote:
> > - printk(" io 0x%lx-0x%lx 0x%lx-0x%lx",
> > + printk(KERN_INFO " requesing the I/O region from 0x%lx-0x%lx 0x%lx-0x%lx",
> Correct spelling is "requesting" and the "from" should either have a
> matching "to" or just be dropped IMHO.
> Personally I'd just make it:
> " requesting I/O region 0x%lx-0x%lx 0x%lx-0x%lx"
[]
> I think the original text was better.
KERN_INFO is the wrong level.
Just log the errors at KERN_ERR/pr_err and make the rest
pr_debug or delete them.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-07-18 15:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <[PATCH]Staging: comedi: fix printk() issue in das16m1.c>
2011-07-18 9:44 ` [PATCH 30/30 v2] Staging: comedi: fix printk() issue in das16m1.c Ravishankar
2011-07-18 9:43 ` Jesper Juhl
2011-07-18 15:46 ` Joe Perches
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®