Remove no-op framework::LockHelper::downgradeWriteAccess

Change-Id: I26c8dbfb2ad3b159d3b32dea450e063f1552d714

1 files changed, 0 insertions, 27 deletions

diff --git a/framework/source/fwi/threadhelp/lockhelper.cxx b/framework/source/fwi/threadhelp/lockhelper.cxx
index e21dee824137..896d821f2a99 100644
--- a/framework/source/fwi/threadhelp/lockhelper.cxx
+++ b/framework/source/fwi/threadhelp/lockhelper.cxx
@@ -209,33 +209,6 @@ void LockHelper::releaseWriteAccess()
 }
 
 /*-************************************************************************************************************
-    @short      downgrade a write access to a read access
-    @descr      A guard should call this method to change a write to a read access.
-                New readers can work too - new writer are blocked!
-
-    @attention  Ignore shareable mutex(!) - because this call never should release a lock completely!
-                We change a write access to a read access only.
-
-    @attention  a) Don't call this method if you are not a writer!
-                    Results are not defined then ...
-                    An upgrade can't be implemented really ... because acquiring new access
-                    will be the same - there no differences!
-                b) Without function ...
-                    because, a mutex don't support it really.
-
-    @seealso    -
-
-    @param      -
-    @return     -
-
-    @onerror    -
-*//*-*************************************************************************************************************/
-void LockHelper::downgradeWriteAccess()
-{
-    // Not supported for mutex!
-}
-
-/*-************************************************************************************************************
     @short      return a reference to a static lock helper
     @descr      Sometimes we need the global mutex or rw-lock! (e.g. in our own static methods)
                 But it's not a good idea to use these global one very often ...