From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/02] OMAP3 clock: Remove virtual clock nodes
Date: Fri, 03 Apr 2009 09:59:21 -0700 [thread overview]
Message-ID: <873acpzn9y.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02FB102C27@dbde02.ent.ti.com> (Rajendra Nayak's message of "Fri\, 3 Apr 2009 21\:49\:58 +0530")
"Nayak, Rajendra" <rnayak@ti.com> writes:
> Hi,
>
> 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.
>
> Patches generated and apply on latest pm branch from Kevin's pm tree.
>
Rajendra,
This series does not apply against the PM branch.
It seems your patches have TABs converted to spaces. For example, in
01/02 the first hunk which removes a bunch of code is trying to remove
lines with spaces and the original code is all TABs, so the patch
fails.
Please resubmit with correct formatting so it applies cleanly.
Kevin
next prev parent reply other threads:[~2009-04-03 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 16:19 [PATCH 00/02] OMAP3 clock: Remove virtual clock nodes Nayak, Rajendra
2009-04-03 16:59 ` Kevin Hilman [this message]
2009-04-07 13:23 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2009-04-17 5:57 Nayak, Rajendra
2009-04-20 16:44 ` Kevin Hilman
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=873acpzn9y.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.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