[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080704090547.GB6848@doriath.ww600.siemens.net>
Date: Fri, 4 Jul 2008 13:05:47 +0400
From: Dmitry Baryshkov <dbaryshkov@...il.com>
To: Ben Dooks <ben-linux@...ff.org>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
Russell King <rmk+lkml@....linux.org.uk>,
Paul Mundt <lethal@...ux-sh.org>,
pHilipp Zabel <philipp.zabel@...il.com>,
Pavel Machek <pavel@....cz>, tony@...mide.com, paul@...an.com,
David Brownell <david-b@...bell.net>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
ian <spyro@....com>
Subject: Re: [PATCH 0/3] Clocklib: generic framework for clocks managing
[v3]
On Thu, Jul 03, 2008 at 09:22:50PM +0100, Ben Dooks wrote:
> On Thu, Jun 26, 2008 at 04:50:33PM +0400, Dmitry Baryshkov wrote:
> > Hi,
> >
> > This is again a set of patches to unify the management of clocks and
> > allow easy registration and unregistration of them. This is neccessary
> > to cleanly support such devices as toshiba mobile companion chips,
> > sa1111 companion, etc. Also it brings code unification, especially for a
> > lot of arm sub-arches which share nearly the same code, etc.
> >
> > This is the "version 3" approach. Given the negative response to
> > kobjects, I've redesigned it to use plain krefs.
> >
> > Debugfs support is merged into main clocklib patch. Documentation
> > for it's interface will come later. For now it provides tree structure
> > with single file per each clock directory.
>
> I'd prefer not to see this called clocklib, it isn't of any use
> outside of the kernel, and once it is in there's little point in
> anyone not using it.
Please propose better name.
>
> --
> Ben (ben@...ff.org, http://www.fluff.org/)
>
> 'a smiley only costs 4 bytes'
--
With best wishes
Dmitry
--
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