This patch converts most common hub diagnostics to use the
device model diagnostic macros ... not all, someone should
reduce the number of err() strings for "bogus hub" cases,
and ideally streamline some of the dozen or so "here's what
this new hub is like" dbg() calls.

For folk running with USB debugging enabled, it also cuts
the useless chatter on connections by deleting the per-poll
success messages and an extra message when things change.
And it deletes a newish diagnostic on an unlink path.

It also makes Pete's new debounce message use the right
port number -- one-based, not zero-based.

Net result: less log clutter because of (a) fewer messages
and (b) fewer long filenames (helps object size too); and
(c) many messages are more useful since they now identify the
particular port (and so device) that's involved.

My main issue with this patch is that it doesn't change
more messages, but it seems reasonable to merge it anyway.
Comments?

- Dave






-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to