From: Karel Zak <kzak@redhat.com>
To: "corentin.labbe" <corentin.labbe@geomatys.fr>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] dmesg.c: print human readable timestamp
Date: Wed, 20 Jul 2011 14:48:26 +0200 [thread overview]
Message-ID: <20110720124826.GA22568@nb.net.home> (raw)
In-Reply-To: <4E2449B6.1070105@geomatys.fr>
On Mon, Jul 18, 2011 at 04:56:54PM +0200, corentin.labbe wrote:
> Perhaps we could keep my patch and add a warning about "problem with
> suspend/resume" (both at first line when -H is used and in
> manpages). Like "Warning timestamp could be inaccurate if you have
> used SUSPEND/RESUME"
I agree.
> If you are agree with that I will update my patch accordingly.
I have already added this feature to the code.
The latest dmesg(1) changes:
* -T, --ctime : print human readable timestamps
[Mon Jul 18 22:30:51 2011] Bluetooth: L2CAP ver 2.15
[Mon Jul 18 22:30:51 2011] Bluetooth: L2CAP socket layer initialized
[Mon Jul 18 22:30:51 2011] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
* -d, --show-delta : display the time spent between messages.
(based on kernel scripts/show_delat).
[ 37.727490 < 0.157379>] Bluetooth: L2CAP ver 2.15
[ 37.729090 < 0.001600>] Bluetooth: L2CAP socket layer initialized
[ 37.964308 < 0.235218>] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
It's possible to mix the options (dmesg -d -T):
[Mon Jul 18 22:30:51 2011 < 0.157379>] Bluetooth: L2CAP ver 2.15
[Mon Jul 18 22:30:51 2011 < 0.001600>] Bluetooth: L2CAP socket layer initialized
[Mon Jul 18 22:30:51 2011 < 0.235218>] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-07-20 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 12:06 [PATCH] dmesg.c: print human readable timestamp corentin.labbe
2011-06-29 14:59 ` Karel Zak
2011-07-18 14:56 ` corentin.labbe
2011-07-20 12:48 ` Karel Zak [this message]
2011-07-20 13:33 ` Voelker, Bernhard
2011-07-20 13:51 ` Karel Zak
2011-07-20 14:25 ` Voelker, Bernhard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110720124826.GA22568@nb.net.home \
--to=kzak@redhat.com \
--cc=corentin.labbe@geomatys.fr \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox