From: masami.hiramatsu.pt@hitachi•com (Masami Hiramatsu)
To: linux-arm-kernel@lists•infradead.org
Subject: arm: kprobe compilation error
Date: Sat, 07 Feb 2015 16:22:47 +0900 [thread overview]
Message-ID: <54D5BD47.4040107@hitachi.com> (raw)
In-Reply-To: <54D38982.6000100@elproma.com.pl>
(2015/02/06 0:17), Janusz U?ycki wrote:
> Hi,
>
> I got the compilation error on next-20150204:
>
> CC arch/arm/probes/kprobes/actions-arm.o
> In file included from arch/arm/probes/kprobes/actions-common.c:18:
> arch/arm/probes/kprobes/core.h:43: error: '[*]' not allowed in other
> than a declaration
> make[2]: *** [arch/arm/probes/kprobes/actions-common.o] B??d 1
> make[2]: *** Oczekiwanie na niezako?czone zadania....
> In file included from arch/arm/probes/kprobes/actions-arm.c:66:
> arch/arm/probes/kprobes/core.h:43: error: '[*]' not allowed in other
> than a declaration
> make[2]: *** [arch/arm/probes/kprobes/actions-arm.o] B??d 1
> In file included from arch/arm/probes/kprobes/core.c:37:
> arch/arm/probes/kprobes/core.h:43: error: '[*]' not allowed in other
> than a declaration
> make[2]: *** [arch/arm/probes/kprobes/core.o] B??d 1
> make[1]: *** [arch/arm/probes/kprobes] B??d 2
> make: *** [arch/arm/probes] B??d 2
>
> reason is *[*]:
> const struct decode_checker *[*]);
Thank you for reporting!
I think there is a typo, it should be "const struct decode_checker *[]".
Thank you,
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com
next prev parent reply other threads:[~2015-02-07 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:17 arm: kprobe compilation error Janusz Użycki
2015-02-07 7:22 ` Masami Hiramatsu [this message]
2015-02-09 9:44 ` Jon Medhurst (Tixy)
2015-02-09 11:00 ` Janusz Użycki
2015-02-10 8:28 ` Wang Nan
2015-02-10 9:36 ` Wang Nan
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=54D5BD47.4040107@hitachi.com \
--to=masami.hiramatsu.pt@hitachi$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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