From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-next@vger.kernel.org, Anders Kaseorg <andersk@mit.edu>,
Jeff Arnold <jbarnold@mit.edu>, Tim Abbott <tabbott@mit.edu>
Subject: linux-next: rr tree build error
Date: Tue, 17 Feb 2009 16:12:52 +1100 [thread overview]
Message-ID: <20090217161252.ef44979c.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Hi Rusty,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
In file included from kernel/kallsyms.c:15:
include/linux/kallsyms.h:22: warning: 'struct module' declared inside parameter list
include/linux/kallsyms.h:22: warning: its scope is only this definition or declaration, which is probably not what you want
kernel/kallsyms.c:164: error: conflicting types for 'kallsyms_on_each_symbol'
include/linux/kallsyms.h:21: error: previous declaration of 'kallsyms_on_each_symbol' was here
kernel/kallsyms.c:181: error: conflicting types for 'kallsyms_on_each_symbol'
include/linux/kallsyms.h:21: error: previous declaration of 'kallsyms_on_each_symbol' was here
Caused by commit eadcd635def320c8f057f32dd3531638ee99e50a ("Ksplice: Add
functions for walking kallsyms symbols").
I have dropped the rr tree for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-17 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 5:12 Stephen Rothwell [this message]
2009-02-17 12:04 ` linux-next: rr tree build error Rusty Russell
2009-02-17 12:27 ` 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=20090217161252.ef44979c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andersk@mit.edu \
--cc=jbarnold@mit.edu \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tabbott@mit.edu \
/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