From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 0B1DFB7B68 for ; Thu, 27 Aug 2009 15:20:59 +1000 (EST) Received: from mail-yw0-f185.google.com (mail-yw0-f185.google.com [209.85.211.185]) by ozlabs.org (Postfix) with ESMTP id 6BD37DDD01 for ; Thu, 27 Aug 2009 15:20:57 +1000 (EST) Received: by ywh15 with SMTP id 15so962201ywh.10 for ; Wed, 26 Aug 2009 22:20:56 -0700 (PDT) MIME-Version: 1.0 Sender: glikely@secretlab.ca In-Reply-To: <1251346157.20467.22.camel@pasglop> References: <1250569288.19007.15.camel@pasglop> <1251346157.20467.22.camel@pasglop> From: Grant Likely Date: Wed, 26 Aug 2009 23:20:36 -0600 Message-ID: Subject: Re: [RFC] Clock binding To: Benjamin Herrenschmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev list , devicetree-discuss@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Aug 26, 2009 at 10:09 PM, Benjamin Herrenschmidt wrote: > On Tue, 2009-08-18 at 14:21 +1000, Benjamin Herrenschmidt wrote: >> So here's a followup to my discussion about the clock API. > > Really nobody has a comment here ? :-) Not even Mitch ? Been wanting too.. a little swamped with kids going back to school tomorrow. Hopefully I'll be able to dig in before the end of the week. g.