[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc64b4640803270633t3b862405sb2708eee25708868@mail.gmail.com>
Date: Thu, 27 Mar 2008 16:33:51 +0300
From: Dmitry <dbaryshkov@...il.com>
To: "Haavard Skinnemoen" <haavard.skinnemoen@...el.com>
Cc: "Russell King" <rmk+lkml@....linux.org.uk>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
hskinnemoen@...el.com, lethal@...ux-sh.org, tony@...mide.com,
paul@...an.com
Subject: Re: [PATCH 1/3] Clocklib: add generic framework for managing clocks.
Hi,
2008/3/27, Haavard Skinnemoen <haavard.skinnemoen@...el.com>:
> On Thu, 27 Mar 2008 13:08:37 +0300
>
> Dmitry <dbaryshkov@...il.com> wrote:
>
>
> > I like this idea! This would also allow to cleanup the references code, etc.
>
>
> Great!
>
>
> > Also after I saw such refactored struct clk, I thought that it looks
> > nearly like kobject. Maybe we should switch to the kobject-based
> > structs? What do you think?
>
>
> I think that would be overkill. We should try to keep this stuff as
> lightweight as possible, and I'm not sure if we can give the kobject
> "parent" field the meaning we want it to have...or use the kref thing
> to do something unrelated to object lifecycle management (i.e. we don't
> want to destroy the object when the refcount goes to zero, we just want
> to stop the clock.)
ACK. Then I'll repost the updated patchset later.
--
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