All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
	John Stultz <john.stultz@linaro.org>,
	Xunlei Pang <pang.xunlei@linaro.org>,
	Baolin Wang <baolin.wang@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Petr Mladek <pmladek@suse.cz>, Tejun Heo <tj@kernel.org>,
	Peter Hurley <peter@hurleysoftware.com>,
	Vasily Averin <vvs@virtuozzo.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH 0/2 v6] printk, Add monotonic and real printk timestamps
Date: Tue, 8 Mar 2016 08:59:42 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1603080858570.3859@nanos> (raw)
In-Reply-To: <1456250040-22351-1-git-send-email-prarit@redhat.com>

On Tue, 23 Feb 2016, Prarit Bhargava wrote:

> This patchset adds monotonic and real printk timestamps.  The first patch
> changes CONFIG_PRINT_TIME from a bool to an int to allow for the additional
> timestamps that are added in patch 2.
> 
> Changes from v6: Petr Mladek pointed out that the current patch
> fails to indicate to userspace programs which timestamp is being used.

How is that solved?

Thanks,

	tglx

  parent reply	other threads:[~2016-03-08  8:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 17:53 [PATCH 0/2 v6] printk, Add monotonic and real printk timestamps Prarit Bhargava
2016-02-23 17:53 ` [PATCH 1/2 v6] lib, switch CONFIG_PRINTK_TIME to int Prarit Bhargava
2016-02-23 17:54 ` [PATCH 2/2 v6] printk, allow different timestamps for printk.time Prarit Bhargava
2016-03-08  7:59 ` Thomas Gleixner [this message]
2016-03-08 11:03   ` [PATCH 0/2 v6] printk, Add monotonic and real printk timestamps Prarit Bhargava
2016-03-10 10:00     ` Petr Mladek
2016-03-10 15:35       ` Thomas Gleixner
2016-04-18 15:30       ` Prarit Bhargava
2016-04-19  8:56         ` Petr Mladek
2016-04-20 17:09           ` Prarit Bhargava
2016-04-21 13:20           ` Prarit Bhargava
2016-04-26 13:00             ` Petr Mladek

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=alpine.DEB.2.11.1603080858570.3859@nanos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pang.xunlei@linaro.org \
    --cc=peter@hurleysoftware.com \
    --cc=pmladek@suse.com \
    --cc=pmladek@suse.cz \
    --cc=prarit@redhat.com \
    --cc=tj@kernel.org \
    --cc=vvs@virtuozzo.com \
    /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.