From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: linux-next: build failure after merge of the final tree (tip tree related)
Date: Wed, 23 Jun 2010 18:55:25 +0200 [thread overview]
Message-ID: <20100623165523.GG5242@nowhere> (raw)
In-Reply-To: <20100624023117.219953e4.sfr@canb.auug.org.au>
Hi Stephen,
On Thu, Jun 24, 2010 at 02:31:17AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sh allnoconfig -
> in fact, all the sh configs) failed like this:
>
> cc1: warnings being treated as errors
> In file included from include/linux/ftrace_event.h:8,
> from include/trace/syscall.h:6,
> from include/linux/syscalls.h:75,
> from arch/sh/kernel/sys_sh32.c:9:
> include/linux/perf_event.h:937: error: 'struct regs' declared inside parameter list
> include/linux/perf_event.h:937: error: its scope is only this definition or declaration, which is probably not what you want
> include/linux/perf_event.h: In function 'perf_fetch_caller_regs':
> include/linux/perf_event.h:952: error: passing argument 1 of 'perf_arch_fetch_caller_regs' from incompatible pointer type
>
> This started after next-20100618.
>
> Caused by commit b0f82b81fe6bbcf78d478071f33e44554726bc81 ("perf: Drop
> the skip argument from perf_arch_fetch_regs_caller") which contained a
> typo in the type of the first argument to perf_arch_fetch_caller_regs()
> in the case that the architecture did not define
> perf_arch_fetch_caller_regs.
There is a pending fix:
From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
[PATCH] perf: Fix argument of perf_arch_fetch_caller_regs
I'm going to send a pull request to Ingo so that gets fixed soon.
Thanks.
next prev parent reply other threads:[~2010-06-23 16:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 16:31 linux-next: build failure after merge of the final tree (tip tree related) Stephen Rothwell
2010-06-23 16:55 ` Frederic Weisbecker [this message]
2010-06-23 23:31 ` Stephen Rothwell
2010-06-24 0:37 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2011-04-12 4:00 Stephen Rothwell
2011-04-12 6:20 ` Ingo Molnar
2011-04-12 6:25 ` David Miller
2010-11-29 2:50 Stephen Rothwell
2010-11-29 22:30 ` Peter Zijlstra
2010-12-07 1:56 ` Stephen Rothwell
2010-11-22 2:39 Stephen Rothwell
2010-11-22 22:00 ` Don Zickus
2010-11-29 2:50 ` Stephen Rothwell
2010-11-29 8:29 ` Ingo Molnar
2010-11-29 14:30 ` Don Zickus
2010-12-07 1:58 ` Stephen Rothwell
2010-12-07 15:37 ` Don Zickus
2010-10-14 5:49 Stephen Rothwell
2010-10-14 6:31 ` Ingo Molnar
2010-09-13 14:29 Stephen Rothwell
2010-09-16 6:32 ` Stephen Rothwell
2010-09-16 6:39 ` Ingo Molnar
2010-09-16 7:08 ` Russell King - ARM Linux
2010-09-16 7:34 ` Ingo Molnar
2010-09-16 9:02 ` Russell King - ARM Linux
2010-09-16 7:09 ` Stephen Rothwell
2010-09-16 7:20 ` Yinghai Lu
2010-09-16 7:27 ` Stephen Rothwell
2010-09-13 14:06 Stephen Rothwell
2010-09-13 19:17 ` Matt Fleming
2010-09-13 19:22 ` Peter Zijlstra
2010-08-02 16:23 Stephen Rothwell
2010-08-02 16:28 ` Russell King
2010-08-02 16:32 ` H. Peter Anvin
2010-08-03 1:07 ` Benjamin Herrenschmidt
2010-08-03 1:42 ` Benjamin Herrenschmidt
2010-08-03 3:13 ` H. Peter Anvin
2010-08-03 4:32 ` Benjamin Herrenschmidt
2010-08-03 5:29 ` Ingo Molnar
2010-08-02 16:28 ` Stephen Rothwell
2010-08-03 1:41 ` Benjamin Herrenschmidt
2010-06-23 0:50 Stephen Rothwell
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=20100623165523.GG5242@nowhere \
--to=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).