1 files changed, 0 insertions, 10 deletions
diff --git a/DESIGN b/DESIGN
index e9d3956..e16ae52 100644
--- a/DESIGN
+++ b/DESIGN
@@ -32,16 +32,6 @@ Issues
    lock/unlock a bad name.  But it does has the benefit to track the access
    to the resources.
 
-   The prototypes of lock_resource/unlock_resource is designed for flexibility.
-   It allows future extension without breaking the ABI.  If that is not a
-   concern (see issue 5),
-
-      void *(*lock_resource)(res_type, void *res);
-      void (*unlock_resource)(res_type, void *res);
-
-   suffice.  And struct st_*_resouce can be removed.  It is a possible
-   simplification.
-
    Another approach is to provide a single lookup_resource call, and make
    functions like eglCreatePbufferFromClientBuffer, which requires a real
    locking mechanism, special cases.