From: Igor Stoppa <igor.stoppa@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
David Brownell <david-b@pacbell.net>,
Paul Walmsley <paul@pwsan.com>,
linux-omap@vger.kernel.org, Felipe Balbi <felipe.balbi@nokia.com>
Subject: Re: [PATCH 1/3] clk: introduce omap_clk_associate
Date: Wed, 15 Oct 2008 00:09:58 +0300 [thread overview]
Message-ID: <1224018598.4977.27.camel@localhost> (raw)
In-Reply-To: <20081014205925.GK8150@atomide.com>
On Tue, 2008-10-14 at 13:59 -0700, ext Tony Lindgren wrote:
> And that we can use same naming in the driver no matter which omap :)
Wasn't that one of the main features of the clock FW, when it was
designed?
--
Cheers, Igor
---
Igor Stoppa
Maemo Software - Nokia Devices R&D - Helsinki
next prev parent reply other threads:[~2008-10-14 21:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 22:47 [PATCH 0/3] omap_clk_associate Felipe Balbi
2008-10-06 22:47 ` [PATCH 1/3] clk: introduce omap_clk_associate Felipe Balbi
2008-10-06 22:47 ` [PATCH 2/3] clk: use clk_associate for musb driver Felipe Balbi
2008-10-06 22:47 ` [PATCH 3/3] clk: use clk_associate on watchdog driver Felipe Balbi
2008-10-14 17:08 ` [PATCH 1/3] clk: introduce omap_clk_associate Paul Walmsley
2008-10-14 17:29 ` Felipe Balbi
2008-10-14 17:47 ` David Brownell
2008-10-14 18:06 ` Felipe Balbi
2008-10-14 20:59 ` Tony Lindgren
2008-10-14 21:09 ` Igor Stoppa [this message]
2008-10-14 21:24 ` Tony Lindgren
2008-10-14 21:28 ` Felipe Balbi
2008-10-15 6:21 ` Högander Jouni
2008-10-15 7:49 ` Paul Walmsley
2008-10-15 12:56 ` Woodruff, Richard
2008-10-15 13:03 ` Högander Jouni
2008-10-15 13:08 ` Paul Walmsley
2008-10-15 22:42 ` Woodruff, Richard
2008-10-15 12:45 ` Woodruff, Richard
2008-10-16 9:02 ` Paul Walmsley
-- strict thread matches above, loose matches on Subject: below --
2008-10-25 19:55 Felipe Balbi
2008-10-25 20:03 ` Felipe Balbi
2008-10-28 1:28 ` Felipe Balbi
2008-11-06 0:53 ` Felipe Balbi
2008-10-25 19:58 Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1224018598.4977.27.camel@localhost \
--to=igor.stoppa@nokia.com \
--cc=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.