linux-kernel - Re: [PATCH on mfd-regulator-power-v3.17] charger: max14577: Fix build breakage when compiled as module

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: <20140924143519.GJ32069@lee--X1>
Date:	Wed, 24 Sep 2014 15:35:19 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc:	Sebastian Reichel <sre@...nel.org>,
	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH on mfd-regulator-power-v3.17] charger: max14577: Fix
 build breakage when compiled as module

On Wed, 24 Sep 2014, Krzysztof Kozlowski wrote:

> The charger's module device table used the same name as regulator driver
> causing a build break when charger was compiled as a module:
> 
> drivers/power/max14577_charger.c:598:1: error: ‘__mod_platform__max14577_regulator_id_device_table’ aliased to undefined symbol ‘max14577_regulator_id’
> make[2]: *** [drivers/power/max14577_charger.o] Error 1
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> Reported-by: kbuild test robot <fengguang.wu@...el.com>
> ---
>  drivers/power/max14577_charger.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I have fixed this up into the original set and re-sent the
pull-request.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/