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, 14 Dec 2012 18:44:31 +0000 (UTC)
From:	Paul Walmsley <paul@...an.com>
To:	Tony Lindgren <tony@...mide.com>, Roger Quadros <rogerq@...com>,
	Benoit Cousson <b-cousson@...com>
cc:	balbi@...com, sameo@...ux.intel.com, keshava_mgowda@...com,
	sshtylyov@...sta.com, bjorn@...k.no, linux-usb@...r.kernel.org,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Rajendra Nayak <rnayak@...com>,
	Mike Turquette <mturquette@...il.com>
Subject: Re: [PATCH v4 16/23] ARM: OMAP2+: clock data: Merge utmi_px_gfclk
 into usb_host_hs_utmi_px_clk

Hi

On Fri, 14 Dec 2012, Tony Lindgren wrote:

> Paul, what about this patch? Looks like you've acked the other clock 
> patches in this series but not this one?

I commented on it briefly here:

https://patchwork.kernel.org/patch/1838111/

Maybe BenoƮt could comment here, but it looks to me (based on a 
superficial look at the hardware clock tree data) that these clock nodes 
should exist.  In an ideal world, we'd be able to get back to the 
autogeneration of this clock data.

Roger, is it a requirement for the driver to remove these clock nodes, or 
is it possible to stick with the existing nodes?


- Paul

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ