Messages in this thread | | | Date | Tue, 20 May 2014 16:56:20 +0530 | Subject | Re: [PATCH v3] PM / OPP: discard duplicate OPPs | From | Viresh Kumar <> |
| |
On 20 May 2014 16:54, Nishanth Menon <nm@ti.com> wrote: > That is upto the caller. returning 0 for an operation we were supposed > to do, but due to error checks, did not do, implies we need to provide > appropriate error back to caller. caller may choose to act upon the > error and do something OR not - depending on what the caller is (for > example, caller may choose to abort the full sequence as it does not > trust the entries anymore, OR maybe trying to add optional OPP - whose > failure is ignored) - it is NOT upto the this code to implement that > policy.
But we aren't talking about failure here. Its not failure. The operation we are trying to do is already done and nothing should break if the OPP was already there or its added now. Its all the same.
| |