On Thu, 9 Mar 2006 13:03:27 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: > "Jesper Juhl" <[EMAIL PROTECTED]> wrote: > > > > > Feb 21 00:12:13 gx110 kernel: gigaset: ISDN_CMD_SETL3: invalid protocol 42 > > > > > > do not provide any useful information for that clientele. They just push > > > > The filename may not be useful to the user, but the instant the user > > decides to > > submit a bugreport to LKML or elsewhere it becomes useful. > > But OTOH, there's a difference between messages-to-developers (usually "the > code went wrong") and messages-to-users (hopefully usually "the hardware > went wrong" or "you went wrong").
Symbol names are generally unique. As a USB stack developer, I never saw the file name being useful for anything in the error message, let alone the full path! Always hated them, but never bothered to break spears over the issue. We have better things to do. I just quietly remove debugging printouts from the code I touch. -- Pete ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
