From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
sedji gaouaou <sedji.gaouaou@atmel.com>
Subject: Re: linux-next: arm tree build failure
Date: Mon, 14 Sep 2009 09:20:05 +0100 [thread overview]
Message-ID: <20090914082005.GB14204@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20090910145944.690c873f.sfr@canb.auug.org.au>
On Thu, Sep 10, 2009 at 02:59:44PM +1000, Stephen Rothwell wrote:
> The next-20090907 and later builds (arm at91cap9adk_defconfig) failed
> like this:
>
> arch/arm/mach-at91/at91cap9_devices.c:821: warning: 'struct atmel_ac97_data' declared inside parameter list
> arch/arm/mach-at91/at91cap9_devices.c:821: warning: its scope is only this definition or declaration, which is probably not what you want
> arch/arm/mach-at91/at91cap9_devices.c:821: error: conflicting types for 'at91_add_device_ac97'
> arch/arm/mach-at91/include/mach/board.h:178: note: previous declaration of 'at91_add_device_ac97' was here
> arch/arm/mach-at91/board-cap9adk.c:367: error: variable 'cap9adk_ac97_data' has initializer but incomplete type
> arch/arm/mach-at91/board-cap9adk.c: In function 'cap9adk_board_init':
> arch/arm/mach-at91/board-cap9adk.c:397: warning: passing argument 1 of 'at91_add_device_ac97' from incompatible pointer type
> arch/arm/mach-at91/include/mach/board.h:178: note: expected 'struct ac97c_platform_data *' but argument is of type 'struct atmel_ac97_data *'
>
> Caused by commit d656f07a7405e788e1275d0238b67f593615f2bb ("ARM: 5640/1:
> This patch modifies the support of AC97 on the at91sam9263 ek board").
No idea. I guess the Atmel folk have split one logical change up between
two trees, and its only been half merged. I don't see anything in the
patch description which mentions this though.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2009-09-14 8:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 4:59 linux-next: arm tree build failure Stephen Rothwell
2009-09-14 8:20 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-28 23:38 Stephen Rothwell
2010-01-29 23:45 ` Russell King
2010-01-30 1:27 ` Stephen Rothwell
2009-04-14 7:48 Stephen Rothwell
2009-04-14 17:09 ` Russell King
2009-02-14 4:27 Stephen Rothwell
2009-02-16 9:23 ` Catalin Marinas
2008-09-18 18:09 Stephen Rothwell
2008-09-18 18:26 ` Eric Miao
2008-09-18 18:33 ` Eric Miao
2008-09-18 22:04 ` Russell King
2008-09-18 22:28 ` Eric Miao
2008-08-19 5:53 Stephen Rothwell
2008-08-19 11:16 ` Marek Vasut
2008-08-19 11:21 ` Takashi Iwai
2008-08-19 16:06 ` Russell King
2008-08-19 16:32 ` Takashi Iwai
2008-08-20 0:01 ` 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=20090914082005.GB14204@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedji.gaouaou@atmel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.