linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the ftrace tree
Date: Thu, 5 Jun 2014 08:20:12 +0800	[thread overview]
Message-ID: <20140605002012.GA10446@localhost> (raw)
In-Reply-To: <20140604122612.366e2874@gandalf.local.home>

On Wed, Jun 04, 2014 at 12:26:12PM -0400, Steven Rostedt wrote:
> On Wed, 4 Jun 2014 16:09:21 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Hi Steven,
> > 
> > After merging the ftrace tree, today's linux-next build (x86_64 allmodconfig)
> > produced this warning:
> > 
> > kernel/trace/trace_benchmark.c: In function 'trace_do_benchmark':
> > kernel/trace/trace_benchmark.c:38:6: warning: unused variable 'seedsq' [-Wunused-variable]
> >   u64 seedsq;
> >       ^
> > 
> > Introduced by commit 81dc9f0ef21e ("tracing: Add tracepoint benchmark tracepoint").
> 
> Hmm, I don't know why my tests missed this. I do a allmodconfig looking
> for new warning messages too. Oh, but I do need to add this config to my
> regular testing config :-/
> 
> I'm surprised Wu's bot didn't report it either.

Steven, it was reported, here is the email archive:

https://lists.01.org/pipermail/kbuild-all/2014-May/004749.html

Thanks,
Fengguang

  parent reply	other threads:[~2014-06-05  0:20 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  6:09 linux-next: build warning after merge of the ftrace tree Stephen Rothwell
2014-06-04 16:26 ` Steven Rostedt
2014-06-04 16:49   ` Stephen Rothwell
2014-06-05  0:20   ` Fengguang Wu [this message]
2014-06-05  1:00     ` Steven Rostedt
2014-06-05  1:03       ` Fengguang Wu
2014-06-05  1:12         ` Steven Rostedt
2014-06-05  1:20           ` Steven Rostedt
2014-06-05  1:33           ` Fengguang Wu
2014-06-05  1:39             ` Steven Rostedt
2014-06-05  2:14               ` Fengguang Wu
2014-06-05  2:36                 ` Steven Rostedt
2014-06-05  2:50                   ` Fengguang Wu
2014-06-05  3:03                   ` Fengguang Wu
2014-06-05  3:13                     ` Steven Rostedt
2014-06-05  3:42                       ` Fengguang Wu
2014-06-05  2:38                 ` Steven Rostedt
2014-06-05  2:44                   ` Fengguang Wu
2014-06-05  2:46                 ` Steven Rostedt
2019-11-15  3:02 Stephen Rothwell
2019-11-15  3:43 ` Steven Rostedt
2020-08-05  4:21 Stephen Rothwell
2020-11-16  6:35 Stephen Rothwell
2020-11-16 17:43 ` Steven Rostedt
2020-11-16 19:24   ` Jonathan Corbet
2020-11-16 20:25     ` Steven Rostedt
2020-11-16 20:29       ` Jonathan Corbet
2020-11-16 20:35         ` Steven Rostedt
2021-08-23  9:58 Stephen Rothwell
2021-08-23 14:00 ` Steven Rostedt
2021-08-24 10:53   ` Stephen Rothwell
2021-10-25  4:39 Stephen Rothwell
2021-10-25  6:13 ` Masami Hiramatsu
2021-10-25 23:35 Stephen Rothwell
2021-10-26 12:15 ` Masami Hiramatsu
2021-10-28 12:23 Stephen Rothwell
2021-10-28 13:16 ` Steven Rostedt
2021-10-28 21:10   ` Stephen Rothwell
2021-10-28 21:29     ` Kalesh Singh
2021-10-28 22:36       ` Stephen Rothwell
2021-10-28 21:30     ` Steven Rostedt
2022-11-25  3:10 Stephen Rothwell
2023-06-23  4:35 Stephen Rothwell
2023-06-23  6:53 ` Donglin Peng

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=20140605002012.GA10446@localhost \
    --to=fengguang.wu@intel.com \
    --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).