From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Lukasz Majewski <l.majewski@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-kernel@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
Shailendra Verma <shailendra.capricorn@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] cpufreq:exynos-cpufreq - Fix for memory leak in case SOC name does not match.
Date: Tue, 09 Jun 2015 16:23:25 +0900 [thread overview]
Message-ID: <5576946D.2070909@samsung.com> (raw)
In-Reply-To: <20150609090722.43965fa0@amdc2363>
On 09.06.2015 16:07, Lukasz Majewski wrote:
> Hi Rafael,
>
>> On Monday, June 08, 2015 10:31:00 AM Lukasz Majewski wrote:
>>> Hi Viresh,
>>>
>>>> On 25-05-15, 07:39, Shailendra Verma wrote:
>>>>> During probe free the memory allocated to "exynos_info" in case
>>>>> of unknown SOC type.
>>>>>
>>>>> Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
>>>>> ---
>>>>> drivers/cpufreq/exynos-cpufreq.c | 6 ++++--
>>>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/drivers/cpufreq/exynos-cpufreq.c
>>>>> b/drivers/cpufreq/exynos-cpufreq.c index 82d2fbb..8682378 100644
>>>>> --- a/drivers/cpufreq/exynos-cpufreq.c
>>>>> +++ b/drivers/cpufreq/exynos-cpufreq.c
>>>>> @@ -182,7 +182,7 @@ static int exynos_cpufreq_probe(struct
>>>>> platform_device *pdev) ret =
>>>>> exynos5250_cpufreq_init(exynos_info); } else {
>>>>> pr_err("%s: Unknown SoC type\n", __func__);
>>>>> - return -ENODEV;
>>>>> + ret = -ENODEV;
>>>>> }
>>>>>
>>>>> if (ret)
>>>>> @@ -190,12 +190,14 @@ static int exynos_cpufreq_probe(struct
>>>>> platform_device *pdev)
>>>>> if (exynos_info->set_freq == NULL) {
>>>>> dev_err(&pdev->dev, "No set_freq function
>>>>> (ERR)\n");
>>>>> + ret = -EINVAL;
>>>>> goto err_vdd_arm;
>>>>> }
>>>>>
>>>>> arm_regulator = regulator_get(NULL, "vdd_arm");
>>>>> if (IS_ERR(arm_regulator)) {
>>>>> dev_err(&pdev->dev, "failed to get resource
>>>>> vdd_arm\n");
>>>>> + ret = -EINVAL;
>>>>> goto err_vdd_arm;
>>>>> }
>>>>>
>>>>> @@ -227,7 +229,7 @@ err_cpufreq_reg:
>>>>> regulator_put(arm_regulator);
>>>>> err_vdd_arm:
>>>>> kfree(exynos_info);
>>>>> - return -EINVAL;
>>>>> + return ret;
>>>>> }
>>>>>
>>>>> static struct platform_driver exynos_cpufreq_platdrv = {
>>>>
>>>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>>>>
>>>
>>> Acked-by: Lukasz Majewski <l.majewski@samsung.com>
>>
>> I'm assuming that it will go it through the Samsung tree.
>>
>>
>
> That would be the easiest way to proceed.
>
> Krzystof would you like to grab this patch?
Sure, I'll take it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-06-09 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 2:09 [PATCH] cpufreq:exynos-cpufreq - Fix for memory leak in case SOC name does not match Shailendra Verma
2015-05-25 7:31 ` Viresh Kumar
2015-06-08 8:31 ` Lukasz Majewski
2015-06-08 23:30 ` Rafael J. Wysocki
2015-06-09 7:07 ` Lukasz Majewski
2015-06-09 7:23 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-23 3:02 Shailendra Verma
2015-05-23 4:42 ` Viresh Kumar
2015-05-21 18:29 Shailendra Verma
2015-05-22 2:17 ` Viresh Kumar
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=5576946D.2070909@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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