public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp•com.au>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Anders Kaseorg <andersk@mit•edu>,
	Jeff Arnold <jbarnold@mit•edu>, Tim Abbott <tabbott@mit•edu>
Subject: Re: linux-next: rr tree build error
Date: Tue, 17 Feb 2009 22:34:14 +1030	[thread overview]
Message-ID: <200902172234.14660.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20090217161252.ef44979c.sfr@canb.auug.org.au>

On Tuesday 17 February 2009 15:42:52 Stephen Rothwell wrote:
> 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

Thanks, this does not happen on x86, I guess some weird include tangle.

Fix is simple (declare struct module), I've done it now.

Thanks,
Rusty.

  reply	other threads:[~2009-02-17 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  5:12 linux-next: rr tree build error Stephen Rothwell
2009-02-17 12:04 ` Rusty Russell [this message]
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=200902172234.14660.rusty@rustcorp.com.au \
    --to=rusty@rustcorp$(echo .)com.au \
    --cc=andersk@mit$(echo .)edu \
    --cc=jbarnold@mit$(echo .)edu \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tabbott@mit$(echo .)edu \
    /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