Re: [PATCH] cpufreq: exynos: Fix for memory leak in case SoC name does not match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>
>>
>> During probe free the memory allocated to "exynos_info" in case of
>> unknown SoC type.
>>
>> Signed-off-by: Shailendra Verma <shailendra.capricorn@xxxxxxxxx>
>> Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
>> Acked-by: Lukasz Majewski <l.majewski@xxxxxxxxxxx>
>> [k.kozlowski: Rebased the patch around if(of_machine_is_compatible)]
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>
>> Signed-off-by: Kukjin Kim <kgene@xxxxxxxxxx>
>> ---
>> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SoC Development]     [Linux Rockchip Development]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Linux SCSI]     [Yosemite News]

  Powered by Linux