1 files changed, 8 insertions, 20 deletions
diff --git a/newlib/libc/stdlib/mlock.c b/newlib/libc/stdlib/mlock.c
index 888c986a9..c603fbcda 100644
--- a/newlib/libc/stdlib/mlock.c
+++ b/newlib/libc/stdlib/mlock.c
@@ -1,7 +1,7 @@
 #ifndef MALLOC_PROVIDED
 /*
 FUNCTION
-<<__malloc_lock>>, <<__malloc_unlock>>---lock malloc pool
+<<__malloc_lock>>, <<__malloc_unlock>>--lock malloc pool
 
 INDEX
 	__malloc_lock
@@ -21,13 +21,13 @@ TRAD_SYNOPSIS
 	struct _reent *<[reent]>;
 
 DESCRIPTION
-The <<malloc>> family of routines call these functions when they need to lock
-the memory pool.  The version of these routines supplied in the library use
-the lock API defined in sys/lock.h.  If multiple threads of execution can
-call <<malloc>>, or if <<malloc>> can be called reentrantly, then you need to
-define your own versions of these functions in order to safely lock the
-memory pool during a call.  If you do not, the memory pool may become
-corrupted.
+The <<malloc>> family of routines call these functions when they need
+to lock the memory pool.  The version of these routines supplied in
+the library does not do anything.  If multiple threads of execution
+can call <<malloc>>, or if <<malloc>> can be called reentrantly, then
+you need to define your own versions of these functions in order to
+safely lock the memory pool during a call.  If you do not, the memory
+pool may become corrupted.
 
 A call to <<malloc>> may call <<__malloc_lock>> recursively; that is,
 the sequence of calls may go <<__malloc_lock>>, <<__malloc_lock>>,
@@ -37,28 +37,16 @@ that it already holds.
 */
 
 #include <malloc.h>
-#include <sys/lock.h>
-
-#ifndef __SINGLE_THREAD__
-__LOCK_INIT_RECURSIVE(static, __malloc_lock_object);
-#endif
 
 void
 __malloc_lock (ptr)
      struct _reent *ptr;
 {
-#ifndef __SINGLE_THREAD__
-  __lock_acquire_recursive (__malloc_lock_object);
-#endif
 }
 
 void
 __malloc_unlock (ptr)
      struct _reent *ptr;
 {
-#ifndef __SINGLE_THREAD__
-  __lock_release_recursive (__malloc_lock_object);
-#endif
 }
-
 #endif