From: "Jan Beulich" <JBeulich@suse.com>
To: "andrii_anisov@epam.com" <andrii_anisov@epam.com>
Cc: Tim Deegan <tim@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
andrii.anisov@gmail.com, Julien Grall <julien.grall@arm.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] perfc: Print a system time in a convenient format
Date: Tue, 11 Sep 2018 08:33:03 -0600 [thread overview]
Message-ID: <5B97D21F02000078001E75A5@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <18c5a856-1291-1096-c7be-9bbcb64d67ab@epam.com>
>>> On 11.09.18 at 16:04, <andrii_anisov@epam.com> wrote:
> So what would be the conclusion?
>
> I'm going to change timestamps format to decimal for all keyhandlers.
> But what about the format itself? Does existing plain ns PRI_stime have
> a chance to be acked?
Well, if everyone else thinks this is a good idea, then I'm sure someone
will ack it (and I certainly wouldn't veto it in such a case).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-11 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 6:53 [PATCH] perfc: Print a system time in a convenient format Andrii Anisov
2018-09-11 8:27 ` Jan Beulich
2018-09-11 8:50 ` Andrii Anisov
2018-09-11 9:10 ` Jan Beulich
2018-09-11 9:15 ` Andrew Cooper
2018-09-11 9:18 ` Jan Beulich
2018-09-11 9:20 ` Andrew Cooper
2018-09-11 9:28 ` Jan Beulich
2018-09-11 9:21 ` Andrii Anisov
2018-09-11 9:30 ` Jan Beulich
2018-09-11 9:49 ` Andrii Anisov
2018-09-11 14:04 ` Andrii Anisov
2018-09-11 14:27 ` George Dunlap
2018-09-11 14:33 ` Jan Beulich [this message]
2018-09-11 9:28 ` George Dunlap
2018-09-11 9:37 ` Jan Beulich
2018-09-11 9:19 ` Andrii Anisov
2018-09-11 9:24 ` George Dunlap
2018-09-11 9:33 ` Jan Beulich
2018-09-11 9:50 ` Andrii Anisov
2018-09-11 9:51 ` George Dunlap
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=5B97D21F02000078001E75A5@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.