From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Kukjin Kim <kgene@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Lukasz Majewski <l.majewski@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Linux PM list <linux-pm@vger.kernel.org>,
shailendra.capricorn@gmail.com
Subject: Re: [PATCH] cpufreq: exynos: Fix for memory leak in case SoC name does not match
Date: Sat, 08 Aug 2015 16:36:34 +0900 [thread overview]
Message-ID: <55C5B182.6000509@samsung.com> (raw)
In-Reply-To: <9283770.jQmuxWnYst@vostro.rjw.lan>
W dniu 06.08.2015 o 09:23, Rafael J. Wysocki pisze:
> On Tuesday, August 04, 2015 04:45:16 PM Kukjin Kim wrote:
>> From: Shailendra Verma <shailendra.capricorn@gmail.com>
>>
>> During probe free the memory allocated to "exynos_info" in case of
>> unknown SoC type.
>>
>> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>> Acked-by: Lukasz Majewski <l.majewski@samsung.com>
>> [k.kozlowski: Rebased the patch around if(of_machine_is_compatible)]
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> Signed-off-by: Kukjin Kim <kgene@kernel.org>
>> ---
>> Hi Rafael and Viresh,
>>
>> Since this is a fix to prevent memory leak, it would be better if
>> this could be sent to linus during -rc via cpufreq tree.
>
> I'm not planning more pull requests for 4.2 and this one doesn't seem to be
> a good enough reason for a pull request of its own, though.
>
> Of course, if there are more urgent fixes, I can push it along with them,
> but there are none so far.
The cpufreq driver will be removed completely in v4.3 or v4.4 with
patchset adding cpufreq-dt support for Exynos 4x12. This means that this
patch makes sense only for 4.2 and as a stable backport (but it was not
marked as such).
Anyone thinks that the patch will be worth stable back-porting?
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-08-08 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 7:45 [PATCH] cpufreq: exynos: Fix for memory leak in case SoC name does not match Kukjin Kim
2015-08-06 0:23 ` Rafael J. Wysocki
2015-08-08 7:36 ` Krzysztof Kozlowski [this message]
2015-08-08 13:29 ` Viresh Kumar
2015-08-14 9:41 ` Rafael J. Wysocki
2015-08-14 9:34 ` Kukjin Kim
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=55C5B182.6000509@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shailendra.capricorn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox