linux-kernel - Re: [PATCH v4 2/3] PM / clock_ops: make __pm_clk

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, 07 Nov 2014 11:25:14 -0800
From:	Kevin Hilman <khilman@...nel.org>
To:	Grygorii Strashko <grygorii.strashko@...com>
Cc:	<ssantosh@...nel.org>, "Rafael J. Wysocki" <rjw@...ysocki.net>,
	<linux-pm@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
	<grant.likely@...retlab.ca>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [PATCH v4 2/3] PM / clock_ops: make __pm_clk_enable more generic

Grygorii Strashko <grygorii.strashko@...com> writes:

> Now there are two places in code which do the same things,
> so allow __pm_clk_enable() to accept pointer on pm_clock_entry
> structure as second parameter instead of pointer on clock and
> remove duplicated code.
>
> Also, updated function intended to be used by following patch.
>
> CC: Santosh Shilimkar <ssantosh@...nel.org>
> CC: Kevin Hilman <khilman@...aro.org>
> CC: Ulf Hansson <ulf.hansson@...aro.org>
> CC: Geert Uytterhoeven <geert@...ux-m68k.org>
> CC: Dmitry Torokhov <dmitry.torokhov@...il.com>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>

Reviewed-by: Kevin Hilman <khilman@...aro.org>
--
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/