From 474b9beeaa5fd6153ffa8ffe10d09acdaa8609da Mon Sep 17 00:00:00 2001
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
Date: Tue, 15 Mar 2016 15:42:57 +0100
Subject: score: Use allocator lock in _Objects_Get_next()

Use the object allocator lock in _Objects_Get_next() instead of disabled
thread dispatching since object creation and deletion is covered by this
lock.

Update #2555.
---
 testsuites/sptests/spobjgetnext/init.c | 2 --
 1 file changed, 2 deletions(-)

(limited to 'testsuites/sptests')

diff --git a/testsuites/sptests/spobjgetnext/init.c b/testsuites/sptests/spobjgetnext/init.c
index 924d65e6e8..c6b8de5a2d 100644
--- a/testsuites/sptests/spobjgetnext/init.c
+++ b/testsuites/sptests/spobjgetnext/init.c
@@ -54,8 +54,6 @@ int scan_objects(
       break;
     /* XXX check dispatch level with macros */
 
-    _Thread_Enable_dispatch();
-
     /* XXX should be able to check that next Id is not one we have seen */
   }
   return i;
-- 
cgit v1.2.3