* printk and kdb - dev_<level> not trapped/forwarded
@ 2014-02-21 23:22 Joe Perches
0 siblings, 0 replies; only message in thread
From: Joe Perches @ 2014-02-21 23:22 UTC (permalink / raw)
To: LKML; +Cc: Andrew Morton, Kay Sievers, Jason Wessel
dev_<level> output does not use printk() but directly
calls vprintk_emit().
kdb only traps direct printk() calls.
So, kdb hasn't emitted any dev_<level> or netdev_<level>
output since structured logging and vprintk_emit() was
introduced a couple of years ago.
It seems no one has cared.
Maybe the kdb handling should be removed?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-02-21 23:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-21 23:22 printk and kdb - dev_<level> not trapped/forwarded Joe Perches
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.