Fix CRYPTO_add_lock documentation.
It's not actually CRYPTO_add_locked, despite the name. I guess they just needed a name that didn't clash with CRYPTO_add. Change-Id: I3fdee08bf75e9a4e1b5e75630707c0be5792599b Reviewed-on: https://boringssl-review.googlesource.com/4102 Reviewed-by: Adam Langley <agl@google.com>
This commit is contained in:
parent
b6d0c6db5e
commit
8056343a58
@ -158,9 +158,7 @@ OPENSSL_EXPORT void CRYPTO_lock(int mode, int lock_num, const char *file,
|
||||
|
||||
/* CRYPTO_add_lock adds |amount| to |*pointer|, protected by the lock specified
|
||||
* by |lock_num|. It returns the new value of |*pointer|. Don't call this
|
||||
* function directly, rather use the |CRYPTO_add_lock| macro.
|
||||
*
|
||||
* TODO(fork): rename to CRYPTO_add_locked. */
|
||||
* function directly, rather use the |CRYPTO_add| macro. */
|
||||
OPENSSL_EXPORT int CRYPTO_add_lock(int *pointer, int amount, int lock_num,
|
||||
const char *file, int line);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user