commit 8056343a58a1253e9a54ea58775b58375b8e3c15
author David Benjamin <davidben@chromium.org> Fri Mar 20 20:13:37 2015 -0400
committer Adam Langley <agl@google.com> Mon Mar 23 23:08:20 2015 +0000
tree 56e7bdc7a534d90324a3ff7fa95894604792da29
parent b6d0c6db5e132f600eae9e70ed97144ad5fab221

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>

include/openssl/thread.h

diff --git a/include/openssl/thread.h b/include/openssl/thread.h
index 453d4b4..cf08dcc 100644
--- a/include/openssl/thread.h
+++ b/include/openssl/thread.h
@@ -158,9 +158,7 @@
 
 /* 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);