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:	Tue, 23 Sep 2014 09:40:12 +0200
From:	Tomeu Vizoso <tomeu.vizoso@...labora.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Mike Turquette <mturquette@...aro.org>,
	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 v12 00/10] Per-user clock constraints

On 09/22/2014 05:06 PM, Russell King - ARM Linux wrote:
> On Mon, Sep 22, 2014 at 04:12:02PM +0200, Tomeu Vizoso wrote:
>> Hello,
>>
>> my branch was finally processed by the 0day build farm and I have fixed the
>> three issues that came up:
> 
> Patch 3 did not come through, so I can't see the changes there.

Yeah, I think all mailing lists choke on it because of its size and the
number of recipients, except linuxppc-dev:

http://patchwork.ozlabs.org/patch/391967/

You were on CC though.

> I'm
> assuming that there's some changes to clkdev in there which I need to
> see.

Nope, that one doesn't touch clkdev.

>> * export __clk_get and __clk_put, so they can be used by clock implementations
>> in modules that previously used clk_get and clk_put.
> 
> This is something I'm not happy about.  We don't want people getting
> access to these low level functions.

I see, will think something about it.

Thanks,

Tomeu

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ