linux-kernel - Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code

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: <571F2AFE.2020006@phytec.de>
Date:	Tue, 26 Apr 2016 10:46:54 +0200
From:	Wadim Egorov <w.egorov@...tec.de>
To:	Heiko Stübner <heiko@...ech.de>
Cc:	Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
	linux-clk@...r.kernel.org, rtc-linux@...glegroups.com,
	devicetree@...r.kernel.org, linux-rockchip@...ts.infradead.org,
	robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	mturquette@...libre.com, sboyd@...eaurora.org,
	lee.jones@...aro.org, lgirdwood@...il.com, a.zummo@...ertech.it,
	alexandre.belloni@...e-electrons.com, dianders@...omium.org,
	zyw@...k-chips.com
Subject: Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's
 simplified DT parsing code



On 26.04.2016 10:17, Heiko Stübner wrote:
> Am Dienstag, 26. April 2016, 09:45:56 schrieb Wadim Egorov:
>> On 25.04.2016 19:39, Mark Brown wrote:
>>> On Mon, Apr 25, 2016 at 03:20:44PM +0200, Wadim Egorov wrote:
>>>> A common simplified DT parsing code for regulators was introduced in
>>>> commit a0c7b164ad11 ("regulator: of: Provide simplified DT parsing
>>>> method")
>>> This doesn't apply against current code, please check and resend.
>> Hm, for me all patches apply to the current code.
>> This patch depends on the first rename patch. Maybe this is the problem?
> which is the reason why renaming stuff makes everything just more complicated 
> without providing additional value ;-) 
>
> The first patch would go through the mfd-tree (if accepted by Lee and Acked by 
> the other involved subsystem maintainers) which would then need a stable 
> branch merged into the regulator tree - or after the first patch goes in you 
> simply wait for a kernel release.
>
> Normally I would expect the reasonable kernel developer to be able to simply 
> read code, kconfig, docs stating the drivers being for rk808 and rk818 without 
> getting "confused" by some structs mentioning the rk808.
>
>
> Heiko
I will drop the first patch and send a v4 later