All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"m.chehab@samsung.com" <m.chehab@samsung.com>,
	"Xie XiuQi" <xiexiuqi@huawei.com>
Subject: Re: [PATCH] tracing: Fix wraparound problems in "uptime" tracer
Date: Fri, 18 Jul 2014 11:54:28 -0700	[thread overview]
Message-ID: <CA+8MBbLhEx9rnoi2ARnc64bHQLy0pWjUZXNNVinudNpqaMPv=g@mail.gmail.com> (raw)
In-Reply-To: <20140718144733.5ef33d64@gandalf.local.home>

On Fri, Jul 18, 2014 at 11:47 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> Do you think this is worthy of stable and 3.16 material?

Perhaps.  Not sure that I need it (I'm stuck waiting for the extlog_trace pieces
which are now queued in "tip", but won't go in until 3.17).  But I suppose we
should minimize the window where people see the bogus wraparound nanoseconds.

-Tony

  reply	other threads:[~2014-07-18 18:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 11:09 [PATCH 0/2] tracing: fix uptime overflow problem Xie XiuQi
2014-06-28 11:10 ` [PATCH 1/2] " Xie XiuQi
2014-06-30 15:10   ` Steven Rostedt
2014-06-30 18:17     ` [PATCH] tracing: Fix wraparound problems in "uptime" tracer Tony Luck
2014-06-30 18:40       ` Steven Rostedt
2014-06-30 20:31         ` [PATCH-v2] " Tony Luck
2014-07-17 23:02           ` Tony Luck
2014-07-18  2:08             ` Steven Rostedt
2014-07-18 17:05               ` Tony Luck
2014-07-18 17:36                 ` Steven Rostedt
2014-07-18 18:43                   ` [PATCH] " Tony Luck
2014-07-18 18:47                     ` Steven Rostedt
2014-07-18 18:54                       ` Tony Luck [this message]
2014-06-28 11:10 ` [PATCH 2/2] tracing: update Documentation/trace/ftrace.txt for uptime Xie XiuQi

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='CA+8MBbLhEx9rnoi2ARnc64bHQLy0pWjUZXNNVinudNpqaMPv=g@mail.gmail.com' \
    --to=tony.luck@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=xiexiuqi@huawei.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.