From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Menon, Nishanth" <nm@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Woodruff, Richard" <r-woodruff2@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Gupta, Ramesh" <grgupta@ti.com>,
Palande Ameya <ameya.palande@nokia.com>
Subject: Re: [PATCH] OMAP:clock: missing list_del for clk_notifier_unregister
Date: Thu, 12 Mar 2009 07:22:13 -0700 [thread overview]
Message-ID: <87mybqakiy.fsf@deeprootsystems.com> (raw)
In-Reply-To: <7A436F7769CA33409C6B44B358BFFF0CFF51DBC4@dlee02.ent.ti.com> (Nishanth Menon's message of "Thu\, 12 Mar 2009 02\:33\:19 -0500")
"Menon, Nishanth" <nm@ti.com> writes:
>> -----Original Message-----
>> From: Paul Walmsley [mailto:paul@pwsan.com]
>> Sent: Thursday, March 12, 2009 9:31 AM
>> To: Menon, Nishanth
>> Cc: linux-omap@vger.kernel.org; Woodruff, Richard; Nayak, Rajendra; Gupta,
>> Ramesh; Palande Ameya
>> Subject: Re: [PATCH] OMAP:clock: missing list_del for
>> clk_notifier_unregister
>
>> Just to clarify, this is currently against the PM branch. There's a new
>
> Yes. This is against the PM branch
>
OK, I'll add this to PM branch...
>> version of the clock notifier patch coming out soon against l-o; will roll
>> this fix in.
And then pull in the new version when it appears.
Kevin
next prev parent reply other threads:[~2009-03-12 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1236790153-9324-1-git-send-email-nm@ti.com>
2009-03-12 7:30 ` [PATCH] OMAP:clock: missing list_del for clk_notifier_unregister Paul Walmsley
2009-03-12 7:33 ` Menon, Nishanth
2009-03-12 14:22 ` Kevin Hilman [this message]
2009-03-11 14:51 DSPBRIDGE+BRIDGE_DVFS: Crashes on multiple reload Menon, Nishanth
2009-03-11 15:27 ` Woodruff, Richard
2009-03-11 16:32 ` Menon, Nishanth
2009-03-11 16:40 ` Woodruff, Richard
2009-03-11 17:59 ` [PATCH] OMAP:clock: missing list_del for clk_notifier_unregister Nishanth Menon
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=87mybqakiy.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=ameya.palande@nokia.com \
--cc=grgupta@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=r-woodruff2@ti.com \
--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