linux-kernel - Re: [PATCH] Fix mc13xxx regulator build on sparc64

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120209220925.GO3058@opensource.wolfsonmicro.com>
Date:	Thu, 9 Feb 2012 22:09:26 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	David Miller <davem@...emloft.net>
Cc:	shawn.guo@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix mc13xxx regulator build on sparc64

On Thu, Feb 09, 2012 at 04:43:01PM -0500, David Miller wrote:

> Since mc13xxx-regulator-core.c and the actual drivers can get built
> into seperate modules, you have to export the DT support symbols
> "mc13xxx_get_num_regulators_dt" and "mc13xxx_parse_regulators_dt"
> otherwise the allmodconfig build fails on sparc64.

Hrm, this was reported in -next and fixed with commit 234393 (regulator:
mc13xxx-regulator-core: Fix the build when driver is selected as module)
but didn't get reported when the commit was first introduced...

Given that allmodconfigs are one of the most commonly tested
configurations for -next I'm wondering both why this didn't get picked
up by any of them and why this is a sparc64 specific issue?

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)