Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1191426 > unrolled thread
| Started by | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| First post | 2015-07-24 03:50 +0200 |
| Last post | 2015-07-24 03:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 2/7] tty: core: Add tty_debug() for printk(KERN_DEBUG) messages Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2015-07-24 03:50 +0200
| From | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| Date | 2015-07-24 03:50 +0200 |
| Subject | Re: [PATCH 2/7] tty: core: Add tty_debug() for printk(KERN_DEBUG) messages |
| Message-ID | <pPAhz-7Ui-11@gated-at.bofh.it> |
On Sun, Jul 12, 2015 at 10:49:08PM -0400, Peter Hurley wrote: > Introduce tty_debug() macro to output uniform debug information for > tty core debug messages (function name and tty name). > > Note: printk(KERN_DEBUG) is retained here over pr_debug() since > messages can be enabled in non-DEBUG builds. But pr_debug() is the "standard" way to enable/disable debugging messages, so I'd really like to see that be used here. Even better, this is a tty device, so it should be using dev_dbg(), which gives us tons of good information built-in for the tty and can properly be parsed by userspace tools to know exactly what device caused what message at what point in time. So I'll take this for now, but moving it to use dev_dbg() would be best eventually. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web