linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c)
Date: Wed, 7 Sep 2016 09:37:00 -0700	[thread overview]
Message-ID: <d6c3b7eb-ba95-1ffa-0453-464e1e24262a@infradead.org> (raw)
In-Reply-To: <20160907175258.1f17a8ba@canb.auug.org.au>

On 09/07/16 00:52, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20160906:
> 

on i386:

../kernel/trace/trace_hwlat.c: In function 'get_sample':
../kernel/trace/trace_hwlat.c:258:18: error: 'struct trace_array' has no member named 'max_latency'
   if (sample > tr->max_latency)
                  ^
../kernel/trace/trace_hwlat.c:259:6: error: 'struct trace_array' has no member named 'max_latency'
    tr->max_latency = sample;
      ^
../kernel/trace/trace_hwlat.c: In function 'hwlat_tracer_init':
../kernel/trace/trace_hwlat.c:583:4: error: 'struct trace_array' has no member named 'max_latency'
  tr->max_latency = 0;
    ^

when CONFIG_TRACER_MAX_TRACE is not enabled.




-- 
~Randy

  reply	other threads:[~2016-09-07 16:37 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 ` Randy Dunlap [this message]
2016-09-07 16:44   ` linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c) 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
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=d6c3b7eb-ba95-1ffa-0453-464e1e24262a@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    /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).