From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c)
Date: Thu, 8 Sep 2016 07:42:01 +1000 [thread overview]
Message-ID: <20160908074201.1ae6c9cc@canb.auug.org.au> (raw)
In-Reply-To: <20160907153810.54f2a9ef@gandalf.local.home>
Hi Steven,
On Wed, 7 Sep 2016 15:38:10 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
>
> commit 64cfdb9788bf3fb2bf6c30701fc3644f25e76df2
> Author: Steven Rostedt (Red Hat) <rostedt@goodmis.org>
> Date: Wed Sep 7 12:45:09 2016 -0400
>
> tracing: Have max_latency be defined for HWLAT_TRACER as well
>
> The hwlat tracer uses tr->max_latency, and if it's the only tracer enabled
> that uses it, the build will fail. Add max_latency and its file when the
> hwlat tracer is enabled.
>
> Link: http://lkml.kernel.org/r/20160907175258.1f17a8ba@canb.auug.org.au
That is not the reporting email ... Randy's was a reply to that one
with message id "<d6c3b7eb-ba95-1ffa-0453-464e1e24262a@infradead.org>".
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-09-07 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:52 linux-next: Tree for Sep 7 Stephen Rothwell
2016-09-07 16:37 ` linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c) Randy Dunlap
2016-09-07 16:44 ` Steven Rostedt
2016-09-07 18:34 ` Randy Dunlap
2016-09-07 18:48 ` Steven Rostedt
2016-09-07 19:38 ` Steven Rostedt
2016-09-07 20:55 ` Randy Dunlap
2016-09-08 2:58 ` Steven Rostedt
2016-09-08 5:38 ` Randy Dunlap
2016-09-07 21:42 ` Stephen Rothwell [this message]
2016-09-08 2:59 ` Steven Rostedt
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=20160908074201.1ae6c9cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).