[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMjpGUeKvP-fJG1sUPRtFDUWCwBg-19JFiFOAKJGmR8Pn4-XUA@mail.gmail.com>
Date: Tue, 10 Apr 2012 23:37:24 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
uclinux-dist-devel@...ckfin.uclinux.org,
Sonic Zhang <Sonic.Zhang@...log.com>,
Bob Liu <lliubbo@...il.com>
Subject: Re: linux-next: triage for April 10, 2012
On Tue, Apr 10, 2012 at 23:09, Paul Gortmaker wrote:
> Thanks Mike, I'll fix the stale link. Here is a RELOC_BFIN_10 fail:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/6087324/
hrm, i'm not seeing that here, but i'm using binutils-2.21. we prob
should file a bug for the Blackfin toolchain guys to investigate.
what version of binutils are you using ?
> Looks like I should go over the bfin fails and check each one, since
> they are somewhat unique -- e.g.
>
> arch/blackfin/mach-bf537/boards/dnp5370.c:392:17: error:
> 'bfin_spi_board_info' undeclared (first use in this function)
>
> in DNP5370_defconfig
blah, looks like something got renamed, but not all the way
commit 7d157fb02bc3f4dc74e6830725864ba501d92da7
blackfin: config: update macro SPI_BFIN in board file
that renamed SPI_BFIN to SPI_BFIN5XX in the board files
but the commit in drivers/spi/ hasn't been merged yet, so it's still
SPI_BFIN there
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists