Seeing which message is printed for which level makes it a lot easier to pick a debug level to narrow down on the data that's interesting.
Signed-off-by: Peter Hutterer <[email protected]> --- src/xf86Wacom.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/xf86Wacom.h b/src/xf86Wacom.h index dbd741c..bcc3b73 100644 --- a/src/xf86Wacom.h +++ b/src/xf86Wacom.h @@ -51,8 +51,8 @@ #define DBG(lvl, priv, ...) \ do { \ if ((lvl) <= priv->debugLevel) { \ - xf86Msg(X_INFO, "%s (%s): ", \ - ((WacomDeviceRec*)priv)->name, __func__); \ + xf86Msg(X_INFO, "%s (%d:%s): ", \ + ((WacomDeviceRec*)priv)->name, lvl, __func__); \ xf86Msg(X_NONE, __VA_ARGS__); \ } \ } while (0) -- 1.7.3.2 ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
