On Mon, Dec 02, 2013 at 02:24:47PM -0500, Peter Hurley wrote: > Add configurable trace support to allow tracing with dev_dbg, > pr_dbg, or trace_printk. Instrument .receive_buf() and read() > paths with traces to aid in debugging flow control changes. > > Signed-off-by: Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> > --- > drivers/tty/n_tty.c | 79 ++++++++++++++++++++++++++++++++++++++++++----------- > 1 file changed, 63 insertions(+), 16 deletions(-) If we are going to do tracing in the tty layer, why not use the in-kernel tracing functionality instead of having this mis-mash of different ways to get tracing data out? I'd much rather prefer that, so I've stopped applying things in this series at this point, I've applied the 6 previous ones. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
