Use "lincan" as syslog messages identification instead of "can.o".
authorppisa <ppisa>
Sun, 9 Jul 2006 23:30:05 +0000 (23:30 +0000)
committerppisa <ppisa>
Sun, 9 Jul 2006 23:30:05 +0000 (23:30 +0000)
lincan/include/main.h
lincan/src/modparms.c

index 7baf67b..fa98bb2 100644 (file)
 #include "./can_queue.h"
 
 #ifdef CAN_DEBUG
-       #define DEBUGMSG(fmt,args...) can_printk(KERN_ERR "can.o (debug): " fmt,\
+       #define DEBUGMSG(fmt,args...) can_printk(KERN_ERR "lincan (debug): " fmt,\
        ##args)
 #else
        #define DEBUGMSG(fmt,args...)
 #endif
 
-#define CANMSG(fmt,args...) can_printk(KERN_ERR "can.o: " fmt,##args)
+#define CANMSG(fmt,args...) can_printk(KERN_ERR "lincan: " fmt,##args)
 
 
 extern can_spinlock_t canuser_manipulation_lock;
index 1782c54..e682113 100644 (file)
@@ -20,7 +20,7 @@ int parse_mod_parms(void)
 
        if ( (hw[0] == NULL) | (io[0] == -1) ) {
                CANMSG("You must supply your type of hardware, interrupt numbers and io address.\n");
-               CANMSG("Example: # insmod can.o hw=pip5 irq=4 io=0x8000\n");
+               CANMSG("Example: # insmod lincan.ko hw=pip5 irq=4 io=0x8000\n");
                return -ENODEV;
        }