From: Steven Rostedt <rostedt@goodmis.org>
To: Fengguang Wu <fengguang.wu@intel.com>
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: Wed, 4 Jun 2014 23:13:51 -0400 [thread overview]
Message-ID: <20140604231351.0ef391cd@gandalf.local.home> (raw)
In-Reply-To: <20140605030334.GA20774@localhost>
On Thu, 5 Jun 2014 11:03:34 +0800
Fengguang Wu <fengguang.wu@intel.com> wrote:
> On Wed, Jun 04, 2014 at 10:36:24PM -0400, Steven Rostedt wrote:
> > On Thu, 5 Jun 2014 10:14:57 +0800
> > Fengguang Wu <fengguang.wu@intel.com> wrote:
> >
> > > > I wonder if the "(Red Hat)" part is causing an issue. Can you send
> > > > directly to my email "rostedt@goodmis.org" and strip the name part?
> > >
> > > OK. I've committed the change. Let's see how well it will work.
> >
> > OK, I never received an error message for my buggy commit I posted
> > before you did this change. I fixed the buggy commit and added another
> > bug. I'll now wait again to see if I get notified.
>
> FYI, we got two error reports
>
> [trace:test-wu-bot 28/29] kernel/trace/trace.c:6683:1: error: expected '; ' before '}' token
> [trace:test-wu-bot 29/29] kernel/trace/trace.c:6701:9: error: 'x' undeclared
>
> in
>
> https://lists.01.org/pipermail/kbuild-all/2014-June/004839.html
> https://lists.01.org/pipermail/kbuild-all/2014-June/004840.html
>
And I received no emails :-(
I wonder why it's failing. What changed since March? I can't think of
anything on my end.
-- Steve
next prev parent reply other threads:[~2014-06-05 3:14 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
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 [this message]
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=20140604231351.0ef391cd@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).