Hi, On Tue, Mar 19, 2019 at 10:12 AM Douglas Anderson <diand...@chromium.org> wrote: > > The things skipped by kdb's "ftdump" command when you pass it a > parameter has always been entries, not lines. The difference usually > doesn't matter but when the trace buffer has multi-line entries (like > a stack dump) it can matter. > > Let's fix this both in the help text for ftdump and also in the local > variable names. > > Signed-off-by: Douglas Anderson <diand...@chromium.org> > Acked-by: Daniel Thompson <daniel.thomp...@linaro.org> > --- > > Changes in v6: None > Changes in v5: > - Add Daniel Thompson Ack. > > Changes in v4: > - skip_lines => skip_entries new for v4. > > Changes in v3: None > > kernel/trace/trace_kdb.c | 16 ++++++++-------- > 1 file changed, 8 insertions(+), 8 deletions(-)
Steven: do you know if/when you plan to take this series? There's no crazy hurry and if you like I can sent a calendar alert to remember to ping you after 5.1 is released so you can land this in a "for 5.3" queue. Just let me know. :-) -Doug _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
