Re: [PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

Hi Viresh, On 04/02/2018 01:32 AM, Viresh Kumar wrote: > On 26-03-18, 16:52, Suman Anna wrote: >> Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when >> failure") has fixed a memory leak in the failure path, however >> kmemleak still keeps reporting a leak even on successful probes. >>

Re: [PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

On 26-03-18, 16:52, Suman Anna wrote: > Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when > failure") has fixed a memory leak in the failure path, however > kmemleak still keeps reporting a leak even on successful probes. > This is a false-positive and is mostly a result of the opp_dat

Re: [PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

On 03/27/2018 05:52 AM, Suman Anna wrote: Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when failure") has fixed a memory leak in the failure path, however kmemleak still keeps reporting a leak even on successful probes. This is a false-positive and is mostly a result of the opp_data

[PATCH] cpufreq: ti-cpufreq: Fix couple of minor issues in probe()

Commit 05829d9431df ("cpufreq: ti-cpufreq: kfree opp_data when failure") has fixed a memory leak in the failure path, however kmemleak still keeps reporting a leak even on successful probes. This is a false-positive and is mostly a result of the opp_data variable not being stored anywhere in the pr