[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150812064309.GL32049@linux>
Date: Wed, 12 Aug 2015 12:13:09 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Rafael Wysocki <rjw@...ysocki.net>, nm@...com,
sboyd@...eaurora.org, linaro-kernel@...ts.linaro.org,
linux-pm@...r.kernel.org, khilman@...aro.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Len Brown <len.brown@...el.com>,
open list <linux-kernel@...r.kernel.org>,
Pavel Machek <pavel@....cz>
Subject: Re: [PATCH V2 1/6] PM / OPP: Free resources and properly return
error on failure
On 11-08-15, 20:11, Dan Carpenter wrote:
> On Tue, Aug 11, 2015 at 08:29:38PM +0530, Viresh Kumar wrote:
> > > This is weird to me, because we are going backwards. What happens if
> > > we goto free_table without adding anything?
> >
> > It will WARN() today.
>
> Then the current code is buggy.
Urg, it wouldn't WARN in this case. Sorry, didn't read it correctly
earlier.
> > > I suspect it's fine, but if
> > > it's a bug then this code still has problems.
> >
> > I don't think we have a bug here, we never added anything and so don't
> > need to free it.
> >
> > > What about if we only increment count when _opp_add_static_v2()
> > > succeeds
> >
> > That's not what we want.
>
> If the first call to _opp_add_static_v2() fails we call
> of_free_opp_table() and you say that triggers a WARN().
No it doesn't.
So, coming back to the point you made about freeing table on !count,
because there were no nodes present in the DT opp table, we have never
tried to add any OPPs. And so there is no need to call
of_free_opp_table() in that case.
Do you still think the current code is wrong ?
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists