linux-kernel - Re: [PATCH v3 0/4] DT clock bindings

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: <20120612154735.GB19410@gmail.com>
Date:	Tue, 12 Jun 2012 08:47:35 -0700
From:	Mike Turquette <mturquette@...com>
To:	Rob Herring <robherring2@...il.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	devicetree-discuss@...ts.ozlabs.org, mturquette@...aro.org,
	s.hauer@...gutronix.de, sboyd@...eaurora.org,
	Rob Herring <rob.herring@...xeda.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	skannan@...eaurora.org, shawn.guo@...aro.org
Subject: Re: [PATCH v3 0/4] DT clock bindings

On 20120612-09:41, Rob Herring wrote:
> From: Rob Herring <rob.herring@...xeda.com>
> 
> This series defines clock bindings for Device-Tree and adds kernel
> support using the common clock infrastructure. The last patch enables
> DT clock support for the Calxeda Highbank platform.
> 
> I'm posting this again to solicit further review. There has been some
> discussion[1], but no definite path forward. This series is not changed
> from the last post other than rebasing to v3.5-rc2.
> 

Hi Rob,

Just FYI, I was following the first thread but it did not seem to reach
resolution.  Namely Saravana seemed to have some lingering concerns.
But I'm definitely not ignoring this series.  I assume you still want
this to go through me once everyone is on board?

Regards,
Mike
--
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/