From d3802bb5d708d01d03774b6758ed1e87484b8fac Mon Sep 17 00:00:00 2001
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
Date: Mon, 20 Apr 2015 09:50:01 +0200
Subject: score: Delete object control block ISR lock

The Objects_Control::Lock was a software layer violation.  It worked
only for the threads since they are somewhat special.

Update #2273.
---
 cpukit/score/include/rtems/score/object.h | 3 ---
 1 file changed, 3 deletions(-)

(limited to 'cpukit/score/include/rtems/score/object.h')

diff --git a/cpukit/score/include/rtems/score/object.h b/cpukit/score/include/rtems/score/object.h
index 36449431d4..70e5fe630c 100644
--- a/cpukit/score/include/rtems/score/object.h
+++ b/cpukit/score/include/rtems/score/object.h
@@ -23,7 +23,6 @@
 #include <rtems/score/basedefs.h>
 #include <rtems/score/cpu.h>
 #include <rtems/score/chain.h>
-#include <rtems/score/isrlock.h>
 
 #ifdef __cplusplus
 extern "C" {
@@ -237,8 +236,6 @@ typedef struct {
   Objects_Id     id;
   /** This is the object's name. */
   Objects_Name   name;
-  /** This is the object's ISR lock. */
-  ISR_LOCK_MEMBER( Lock )
 } Objects_Control;
 
 #if defined( RTEMS_MULTIPROCESSING )
-- 
cgit v1.2.3