commit a1ffbb84cf0f7f75ccb84fa6e0752b645b81ebdf
author Manojkiran Eda <manojkiran.eda@gmail.com> Wed Oct 28 17:42:21 2020 +0530
committer ManojKiran Eda <manojkiran.eda@gmail.com> Thu Oct 29 04:35:05 2020 +0000
tree de6bbd631683d6303ab5e51536f80315a51da5d7
parent 10f0d240a56e33acf78dae93fa6f71387f2e2af2

Fix Release Lock API

- 3174e4dfd3185c131a07371b4b5a5b40cf0e0bdb commit had broke the
  release lock api. This small change has been overlooked in the
  commit during the refactoring.

- status is a bool & status2 would be of type RcReleaseLockApi.As part of
  refactoring instead of status2 we were returning status(bool) as a parameter
  in the pair.

Tested By:

- Functional Lock Testing & openbmc-test-automation passed.
(openbmc-test-automation/openpower/ext_interfaces/test_lock_management.robot)

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I71334dc863023cd40e9d813a5fa147493f5c3f9f

include/ibm/locks.hpp

diff --git a/include/ibm/locks.hpp b/include/ibm/locks.hpp
index a8513f6..3054791 100644
--- a/include/ibm/locks.hpp
+++ b/include/ibm/locks.hpp
@@ -325,7 +325,7 @@
         // them
         releaseLock(p);
     }
-    return std::make_pair(true, status);
+    return std::make_pair(true, status2);
 }
 
 inline RcAcquireLock Lock::acquireLock(const LockRequests& lockRequestStructure)