From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, Jean Pihet <jpihet@mvista.com>
Subject: Re: [PATCH 00/02] OMAP3 clock: Remove virtual clock nodes
Date: Mon, 20 Apr 2009 11:44:21 -0500 [thread overview]
Message-ID: <87ocurcm1m.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02FB251DD1@dbde02.ent.ti.com> (Rajendra Nayak's message of "Fri\, 17 Apr 2009 11\:27\:42 +0530")
"Nayak, Rajendra" <rnayak@ti.com> writes:
> Resending this patch-set with some issues of tabs-to-spaces reported by Kevin Hilman
> fixed and also some warning removals from Jean Pihet.
>
> Patches apply on latest linux-omap pm branch +
> [PATCH 00/10] OMAP3: SR: Fixes in Smartreflex driver sent on 04/15/09
> http://marc.info/?l=linux-omap&m=123980012121460&w=2
>
Thanks, pushing this whitespace-fixed version of series to PM branch
today.
Kevin
>
> This patch set removes the virtual clock node implementation for
> VDD1/2 on omap3 which was causing issues with recursive locking of spinlocks.
> All references to virtual clock nodes from resource framework and cpufreq
> driver are removed. Resource framework now uses individual dpll clock
> nodes to do frequency scaling.
> Most of the functionality implemented as part of the virtual clock nodes
> is now implemented internally in the resource framework.
>
> Thanks to Tero Kristo <tero.kristo@nokia.com> who has implemented
> most of these changes.
>
> regards,
> Rajendra
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-20 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 5:57 [PATCH 00/02] OMAP3 clock: Remove virtual clock nodes Nayak, Rajendra
2009-04-20 16:44 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-03 16:19 Nayak, Rajendra
2009-04-03 16:59 ` Kevin Hilman
2009-04-07 13:23 ` Jean Pihet
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=87ocurcm1m.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=jpihet@mvista.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox