From: Zumeng Chen <zumeng.chen@windriver.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, rjw@rjwysocki.net, d-gerlach@ti.com,
tony@atomide.com
Subject: Re: [PATCH ] cpufreq: ti-cpufreq: kfree opp_data when failure
Date: Mon, 9 Oct 2017 13:51:00 +0800 [thread overview]
Message-ID: <5dbd2161-1cef-01c4-ac3a-19fcd4cc19f7@windriver.com> (raw)
In-Reply-To: <20171004053642.GA8478@vireshk-i7>
On 10/04/2017 01:36 PM, Viresh Kumar wrote:
> On 28-09-17, 13:00, Zumeng Chen wrote:
>> Yes, you are right, it seems of_node_put(np) that you mentioned were
>> ignored by both paths. If you don't mind I can deliver a separate patch
>> to fix this based on some testing later.
> Yeah, that's exactly how I want it.
>
OK, I'll do it when I'm back from vacation, thanks ~
WARNING: multiple messages have this Message-ID (diff)
From: zumeng.chen@windriver.com (Zumeng Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH ] cpufreq: ti-cpufreq: kfree opp_data when failure
Date: Mon, 9 Oct 2017 13:51:00 +0800 [thread overview]
Message-ID: <5dbd2161-1cef-01c4-ac3a-19fcd4cc19f7@windriver.com> (raw)
In-Reply-To: <20171004053642.GA8478@vireshk-i7>
On 10/04/2017 01:36 PM, Viresh Kumar wrote:
> On 28-09-17, 13:00, Zumeng Chen wrote:
>> Yes, you are right, it seems of_node_put(np) that you mentioned were
>> ignored by both paths. If you don't mind I can deliver a separate patch
>> to fix this based on some testing later.
> Yeah, that's exactly how I want it.
>
OK, I'll do it when I'm back from vacation, thanks ~
next prev parent reply other threads:[~2017-10-09 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 7:08 [PATCH ] cpufreq: ti-cpufreq: kfree opp_data when failure Zumeng Chen
2017-09-27 7:08 ` Zumeng Chen
2017-09-27 17:40 ` Viresh Kumar
2017-09-27 17:40 ` Viresh Kumar
2017-09-27 23:49 ` Zumeng Chen
2017-09-27 23:49 ` Zumeng Chen
2017-09-28 4:19 ` Viresh Kumar
2017-09-28 4:19 ` Viresh Kumar
2017-09-28 5:00 ` Zumeng Chen
2017-09-28 5:00 ` Zumeng Chen
2017-10-04 5:36 ` Viresh Kumar
2017-10-04 5:36 ` Viresh Kumar
2017-10-09 5:51 ` Zumeng Chen [this message]
2017-10-09 5:51 ` Zumeng Chen
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=5dbd2161-1cef-01c4-ac3a-19fcd4cc19f7@windriver.com \
--to=zumeng.chen@windriver.com \
--cc=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.org \
/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.