linux-kernel - Re: [PATCH v13 0/9] Per-user clock constraints

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: <5421DF46.2010107@codeaurora.org>
Date:	Tue, 23 Sep 2014 13:59:50 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Tomeu Vizoso <tomeu.vizoso@...labora.com>,
	Mike Turquette <mturquette@...aro.org>
CC:	Russell King <linux@....linux.org.uk>,
	Stephen Warren <swarren@...dotorg.org>,
	Peter De Schrijver <pdeschrijver@...dia.com>,
	linux-kernel@...r.kernel.org, tomasz.figa@...il.com, rabin@....in,
	Thierry Reding <thierry.reding@...il.com>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v13 0/9] Per-user clock constraints

On 09/23/14 11:40, Tomeu Vizoso wrote:
> Hello,
>
> this version of the patchset addresses some issues that Russell pointed out
> yesterday:
>
> * Refactor the changes to clkdev.c to reduce the amount of ifdefs.
>
> * Properly release clocks when there isn't enough memory to create the per-user
> wrapper.
>
> * Add clk_provider_put(struct clk_core*) for clock implementations to call
> instead of clk_put(struct clk*) (instead of exposing __clk_put).
>
> As the previous versions, this is based on top of 3.17-rc4 and Mike's patch at
> [0].

Any thoughts on my comments on patch set #10[1]? It seems like we can
avoid having a flag day to support this.

[1] https://lkml.org/lkml/2014/9/9/960

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

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