From 975bc1026d1162107e04e9820e41621945b74023 Mon Sep 17 00:00:00 2001 From: Karel Zak Date: Thu, 5 Apr 2018 15:59:59 +0200 Subject: [PATCH] dmesg: fix raw output The commit 5f538ac40c0d215b6c9a881effe4c3b214366715 has introduced regression ("goto" to the wrong place, so timestamps in raw mode is not printed at all). Addresses: https://github.com/karelzak/util-linux/issues/614 Signed-off-by: Karel Zak --- sys-utils/dmesg.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/sys-utils/dmesg.c b/sys-utils/dmesg.c index 22c381c1d2..ba4e225283 100644 --- a/sys-utils/dmesg.c +++ b/sys-utils/dmesg.c @@ -906,7 +906,7 @@ static void print_record(struct dmesg_control *ctl, LOG_MAKEPRI(rec->facility, rec->level), (long) rec->tv.tv_sec, (long) rec->tv.tv_usec); - goto mesg_output; + goto full_output; } /* Store decode information (facility & priority level) in a buffer */ @@ -1008,7 +1008,6 @@ full_output: color_disable(); } -mesg_output: /* * A kernel message may contain several lines of output, separated * by '\n'. If the timestamp and decode outputs are forced then each -- 2.47.3