linux-kernel - Re: [PATCH 2/3] regulator: MAX77686: Add Maxim 77686 regulator driver

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: <20120523100347.GF4085@opensource.wolfsonmicro.com>
Date:	Wed, 23 May 2012 11:03:47 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	jonghwa3.lee@...sung.com
Cc:	linux-kernel@...r.kernel.org,
	Alessandro Zummo <a.zummo@...ertech.it>,
	Samuel Oritz <sameo@...ux.intel.com>,
	Liam Girdwood <trg@...com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Chanwoo Choi <cw00.choi@...sung.com>,
	Chiwoong Byun <woong.byun@...sung.com>
Subject: Re: [PATCH 2/3] regulator: MAX77686: Add Maxim 77686 regulator driver

On Wed, May 23, 2012 at 09:40:44AM +0900, jonghwa3.lee@...sung.com wrote:

> I tried to change API to generic version but it got problem because of
> overlapping. As you know almost of boards uses private clock API not
> generic. So how do you think can i test it without modifying board file?
> I'm afraid of changing all clock registering is too expensive.

I've been using x86 to do build tests, though it's not so useful for
testing and you do need to enable the API since the x86 maintainers have
been ignoring my patches to do so.  The other option would be to just
drop the support for the clock enables until the clock API is available
on a paltform you have.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)