Use the dev_printk() routines to output the kernel messages in the
attach routine.

The main 'attach' message had a level of KERN_ERR, I believe it should
have been KERN_INFO. Also, move that message to the end of the attach
so it only gets displayed if the attach is successful.

Signed-off-by: H Hartley Sweeten <[email protected]>
Cc: Ian Abbott <[email protected]>
Cc: Frank Mori Hess <[email protected]>
Cc: Greg Kroah-hartman <[email protected]>
---
 drivers/staging/comedi/drivers/ni_daq_700.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/comedi/drivers/ni_daq_700.c 
b/drivers/staging/comedi/drivers/ni_daq_700.c
index 94cb346..50fad12 100644
--- a/drivers/staging/comedi/drivers/ni_daq_700.c
+++ b/drivers/staging/comedi/drivers/ni_daq_700.c
@@ -113,11 +113,8 @@ static int dio700_attach(struct comedi_device *dev, struct 
comedi_devconfig *it)
                return -EIO;
        iobase = link->resource[0]->start;
 
-       printk(KERN_ERR "comedi%d: ni_daq_700: %s, io 0x%lx\n", dev->minor,
-              thisboard->name, iobase);
-
        if (iobase == 0) {
-               printk(KERN_ERR "io base address is zero!\n");
+               dev_err(dev->class_dev, "io base address is zero!\n");
                return -EINVAL;
        }
 
@@ -142,6 +139,11 @@ static int dio700_attach(struct comedi_device *dev, struct 
comedi_devconfig *it)
        s->state        = 0;
        s->io_bits      = 0x00ff;
 
+       dev_info(dev->class_dev, "%s: %s, io 0x%lx\n",
+               dev->driver->driver_name,
+               dev->board_name,
+               dev->iobase);
+
        return 0;
 };
 
-- 
1.7.11

_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel

Reply via email to