linux-kernel - Re: linux-next: build failure after merge of the l2-mtd tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 May 2014 10:42:25 -0700
From:	Brian Norris <computersforpeace@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Artem Bityutskiy <dedekind1@...il.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Vincenzo Aliberti <vincenzo.aliberti@...il.com>
Subject: Re: linux-next: build failure after merge of the l2-mtd tree

Hi Stephen,

On Thu, May 22, 2014 at 03:30:47PM +1000, Stephen Rothwell wrote:
> Hi Artem,

FYI, I'm managing this tree now, not Artem.

> After merging the l2-mtd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/mtd/lpddr/lpddr2_nvm.c: In function 'ow_enable':
> drivers/mtd/lpddr/lpddr2_nvm.c:149:2: error: implicit declaration of function 'writel_relaxed' [-Werror=implicit-function-declaration]
>   writel_relaxed(build_mr_cfgmask(pcm_data->bus_width) | 0x18,
>   ^
> 
> Caused by commit 96ba9dd65788 ("mtd: lpddr: add driver for LPDDR2-NVM
> PCM memories").

Vincenzo and I have already identified the build failure. It's because
the I/O accessors are not implemented uniformly across architectures.
I just pushed a patch to restrict this driver to ARM for now, but I hope
this inconsistency will be improved soon. (I believe there's a patch
series out there right now.)

> I have used the l2-mtd tree from next-20140521 for today.

Thanks, and thanks for the report.

Regards,
Brian
--
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/