[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponfdoPG7H4h-5s+V7CwB_SgnyqqUm9aa6G-K_cX3DOcfA@mail.gmail.com>
Date: Wed, 14 May 2014 16:38:10 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Chander Kashyap <chander.kashyap@...aro.org>
Cc: Nishanth Menon <nm@...com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chander Kashyap <k.chander@...sung.com>,
Inderpal Singh <inderpal.s@...sung.com>
Subject: Re: [PATCH] PM / OPP: discard duplicate OPP additions
On 14 May 2014 15:01, Chander Kashyap <chander.kashyap@...aro.org> wrote:
>> say we do at this point:
>> if (new_opp->rate == opp->rate) {
>> dev_err(dev, "%s: attempt to add duplicate OPP entry (rate=%ld)\n",
>> __func__, new_opp->rate)
>> kfree(new_opp);
>> return -EINVAL;
>> }
>
> Yes this is more cleaner.
> But instead of dev_err, we should use dev_warn and secondly
Correct
> return 0 rather than EINVAL, as there are independent users for this function
Why? We should actually use EEXIST here instead of EINVAL though..
--
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