On Sat, 05 Jan 2008 12:41:16 +0100, [EMAIL PROTECTED] said:
[...]
> 
> modprobe -r keyspan:
>  usbcore: deregistering interface driver keyspan
>  drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Keyspan
>  - (without firmware)
>  drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Keyspan
>  1 port adapter
>  drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Keyspan
>  2 port adapter
>  drivers/usb/serial/usb-serial.c: USB Serial deregistering driver Keyspan
>  4 port adapter
>  usbcore: deregistering interface driver usbserial_generic
>  drivers/usb/serial/usb-serial.c: USB Serial deregistering driver generic
>  usbcore: deregistering interface driver usbserial
> 
> from my admin`s point of view, "drivers/usb/serial/usb-serial.c" is
> useless clutter which generates an overhead of ~30% here and makes
> reading dmesg more difficult.

I couldn't agree more. :-)

> is there a special reason why there is a path to a sourcefile being
> printed here ?

The reason is that this driver uses the info() etc. macros from
linux/usb.h
which in turn use the __FILE__ macro for showing the source file name.
With the current kernel build mechanism, that expands to the path you
are
seeing. (I gather it wasn't so in 2.4 times.) I tried to submit a patch
for that
but it got rejected because these macros are apparently deprecated.

> what`s the advantage of having this and not just "usb-serial:" instead ?

Easier coding - or rather, avoiding the work of re-coding. The info()
macro
is there, it works, why change it?

> can this probable be optimized (as most drivers only print  "drivername:"
> anyway) ?

See the redefinition of these macros in drivers/isdn/gigaset/gigaset.h
for
the alternative I proposed at the time.

HTH
Tilman
-- 
  Tilman Schmidt
  [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to