[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 1/1] Add module_semaphore_free() to destroy semaphore...
From: |
sub |
Subject: |
[PATCH 1/1] Add module_semaphore_free() to destroy semaphore... |
Date: |
Fri, 9 Dec 2011 06:05:33 +0400 |
>>> you mean just to remove module_semaphore_init completely and use
>>> static sem_t my_sem;
>>> in the modules instead of
>>> static sem_t *my_sem;
>>
>> yup :)
> Ok.
> Anatol, would you mind resubmitting your patch based on Trev's comments?
Ok.
To tell the truth , the use of platform-specific functions instead of the
wrappers (such as module_semaphore_...) is strange to me.
I proceeded from the assumption that the design of a module API develops
towards wrapping the platform specific calls, to say nothing of the hiding the
semaphore's implementation.
Anatol.
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., sub, 2011/12/07
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Trevor Saunders, 2011/12/07
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Andrei Kholodnyi, 2011/12/07
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Trevor Saunders, 2011/12/07
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Andrei Kholodnyi, 2011/12/08
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore...,
sub <=
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Trevor Saunders, 2011/12/08
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., sub, 2011/12/09
- [PATCH 1/1] Add module_semaphore_free() to destroy semaphore..., Trevor Saunders, 2011/12/09