linux-kernel - Re: [PATCH] mfd : dbx500 : fix compilation error

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: <20120416144213.GC24130@sortiz-mobl>
Date:	Mon, 16 Apr 2012 16:42:13 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:	srinidhi.kasagar@...ricsson.com, linus.walleij@...ricsson.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mfd : dbx500 : fix compilation error

Hi Daniel,

On Mon, Apr 02, 2012 at 05:55:48PM +0200, Daniel Lezcano wrote:
> The ux500 default config enables the db5500 and the db8500.
> The incoming cpuidle driver uses the 'prcmu_enable_wakeups'
> and the 'prcmu_set_power_state' functions but these ones
> are defined but not implemented for the db5500, leading to
> an unresolved symbol error at link time. In order to compile,
> we have to disable the db5500 support which is not acceptable
> for the default config.
> 
> I noticed there are also some other functions which are
> defined but not implemented.
> 
> This patch fix this by removing the functions definitions
> and move out of the config section the empty functions which
> are normally used when the DB550 config is disabled.
> Only the functions which are not implemented are concerned
> by this modification.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@...aro.org>
Applied to my for-linus branch, thanks.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/