From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>,
"David Brownell" <david-b@pacbell.net>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "Bryan Wu" <bryan.wu@analog.com>, linux-kernel@vger.kernel.org
Subject: Re: blackfin compile error
Date: Sun, 2 Dec 2007 14:42:40 +0800 [thread overview]
Message-ID: <386072610712012242i58e48aebk17fec7a87391a7fc@mail.gmail.com> (raw)
In-Reply-To: <20071202004204.GE15974@stusta.de>
On Dec 2, 2007 8:42 AM, Adrian Bunk <bunk@kernel.org> wrote:
> It seems commit 5d448dd50712ae42f8176b5bb8db4703bef6f0f5 was incomplete:
>
> <-- snip -->
>
> ...
> CC arch/blackfin/mach-bf537/boards/stamp.o
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/blackfin/mach-bf537/boards/stamp.c:539: error: unknown field 'pin_req' specified in initializer
Yes, there is a SPI patch adding the field 'pin_req' in a Blackfin SPI
header file which is in -mm tree.
David, could you please submit the Blackfin SPI update to mainline?
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/blackfin/mach-bf537/boards/stamp.c:539: error: extra brace group at end of initializer
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/blackfin/mach-bf537/boards/stamp.c:539: error: (near initialization for 'bfin_spi0_info')
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/blackfin/mach-bf537/boards/stamp.c:539: warning: excess elements in struct initializer
> /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/blackfin/mach-bf537/boards/stamp.c:539: warning: (near initialization for 'bfin_spi0_info')
> make[2]: *** [arch/blackfin/mach-bf537/boards/stamp.o] Error 1
>
> <-- snip -->
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2007-12-02 6:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 0:42 blackfin compile error Adrian Bunk
2007-12-02 6:42 ` Bryan Wu [this message]
2007-12-02 6:59 ` David Brownell
2007-12-02 7:05 ` Andrew Morton
2007-12-03 1:30 ` David Brownell
2008-02-06 15:18 Adrian Bunk
2008-02-06 16:23 ` Matt Mackall
2008-02-06 19:12 ` Robin Getz
2008-02-06 19:37 ` Andrew Morton
2008-02-07 7:26 ` Bryan Wu
2008-02-07 16:03 ` Mike Frysinger
2008-02-07 19:37 ` Bryan Wu
2008-02-07 20:31 ` Mike Frysinger
2008-02-07 21:32 ` Robin Getz
2008-02-08 5:25 ` Mike Frysinger
2008-02-08 18:53 ` Bryan Wu
2008-02-08 20:04 ` Mike Frysinger
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=386072610712012242i58e48aebk17fec7a87391a7fc@mail.gmail.com \
--to=cooloney.lkml@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=bunk@kernel.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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).