linux-kernel - Re: [PATCH] regulator: core: mark lock functions as __maybe

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: <20151007140121.GB7858@pengutronix.de>
Date:	Wed, 7 Oct 2015 16:01:21 +0200
From:	Sascha Hauer <s.hauer@...gutronix.de>
To:	Mark Brown <broonie@...nel.org>
Cc:	Arnd Bergmann <arnd@...db.de>, Liam Girdwood <lgirdwood@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: core: mark lock functions as __maybe_unused

On Wed, Oct 07, 2015 at 11:24:07AM +0100, Mark Brown wrote:
> On Wed, Oct 07, 2015 at 12:12:09PM +0200, Arnd Bergmann wrote:
> 
> > The best way to avoid these would be to add the code that will
> > use these functions. If that still takes a while, this patch
> > at least shuts up the compiler by marking the functions
> > as __maybe_unused. The same could be achieved by marking them
> > as static inline or non-static, or by hiding them from the
> > compiler, but those seemed less appropriate.
> 
> That code is still in review, it's not looking too hard to get merged.

I'll send an update on that next week after ELCE.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/