linux-kernel - Re: [PATCH] regulator: fix tps6524x section mismatch

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] [day] [month] [year] [list]

Message-ID: <1301148531.3455.48.camel@odin>
Date:	Sat, 26 Mar 2011 14:08:51 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Cyril Chemparathy <cyril@...com>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH] regulator: fix tps6524x section mismatch

On Thu, 2011-03-24 at 13:30 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@...cle.com>
> 
> Fix section mismatch that is caused by init code calling exit code:
> pmic_remove() cannot be marked as __devexit.
> 
> WARNING: drivers/regulator/tps6524x-regulator.o(.devinit.text+0x205): Section mismatch in reference from the function pmic_probe() to the function .devexit.text:pmic_remove()
> The function __devinit pmic_probe() references
> a function __devexit pmic_remove().
> This is often seen when error handling in the init function
> uses functionality in the exit path.
> The fix is often to remove the __devexit annotation of
> pmic_remove() so it may be used outside an exit section.
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> Cc:	Liam Girdwood <lrg@...mlogic.co.uk>
> Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
> Cc:	Cyril Chemparathy <cyril@...com>
> ---
>  drivers/regulator/tps6524x-regulator.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied.
Thanks

Liam

--
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/