linux-kernel - Re: Patch to add mioa701 glue for voltage regulation

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]

Date:	Fri, 24 Apr 2009 10:42:16 +0100
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	broonie@...nsource.wolfsonmicro.com, eric.miao@...vell.com,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, philipp.zabel@...il.com
Subject: Re: Patch to add mioa701 glue for voltage regulation

On Thu, 2009-04-23 at 20:30 +0200, Robert Jarzmik wrote:
> Hi Mark and Eric,
> 
> I have that patch which adds voltage regulation definitions to mioa701
> board. The trick is, this patch depends on two others :
> 
>  - one which will be merged through Mark's regulator tree.
>    This one is mandatory as a compiling dependency exists through include files.
> 
>  - one which will be merge through Eric pxa tree.
>    This is the cpufreq one, and has a "very weak" dependency, as only the
>    "vcc_core" name _is_ the dependency.
> 
> I think the easiest way to solve the compiling dependency
> (include/linux/regulator.max1586.h) is to make that patch go through regulator
> tree as well for linux-next, even if it's arm machine specific, don't you ?
> 

If fine with this going through regulator providing I get an ACK from
Eric.

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/