linux-kernel - Re: [PATCH] regulator: Copy constraints from regulators when initialising them

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]

Date:	Tue, 30 Nov 2010 15:15:03 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH] regulator: Copy constraints from regulators when
 initialising them

On Mon, 2010-11-29 at 15:55 +0000, Mark Brown wrote:
> Currently the regulator API uses the constraints structure passed in to
> the core throughout the lifetime of the object. This means that it is not
> possible to mark the constraints as __initdata so if the kernel supports
> many boards the constraints for all of them are kept around throughout the
> lifetime of the system, consuming memory needlessly. By copying constraints
> that are actually used we allow the use of __initdata, saving memory when
> multiple boards are supported.
> 
> This also means the constraints can be const.
> 
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>

Applied.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

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