linux-kernel - Re: [PATCH 2/6] ARM: tegra20: Separate out clk ops and clk data

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: <4FEC965F.4060104@wwwdotorg.org>
Date:	Thu, 28 Jun 2012 11:37:35 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Prashant Gaikwad <pgaikwad@...dia.com>
CC:	mturquette@...com, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org,
	linux@....linux.org.uk, ccross@...roid.com, olof@...om.net
Subject: Re: [PATCH 2/6] ARM: tegra20: Separate out clk ops and clk data

On 06/28/2012 04:37 AM, Prashant Gaikwad wrote:
> Move clock initialization data to separate file. This is
> required for migrating to generic clock framework if static
> initialization is used.
> 
> TODO: Add clock suspend/resume support

Is the suspend/resume code something that was present in the existing
Tegra clock code? If not, I'd be tempted to just drop that TODO line
from the patch description when applying this.
--
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/