diff options
| author | Salvatore Sanfilippo <antirez@gmail.com> | 2020-02-27 10:01:48 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-27 10:01:48 +0100 |
| commit | 37612118c8c0b2afb2df10fad6c91b4773434c6f (patch) | |
| tree | 12142c5c351e50e35191f2b77411d281e75a99aa | |
| parent | 049969971e78ecfc87456cbacf389858d8cbf14b (diff) | |
| parent | 28bde891723b2bd815663d3228b28376b1e0dcb9 (diff) | |
| download | redis-37612118c8c0b2afb2df10fad6c91b4773434c6f.tar.gz | |
Merge pull request #6919 from ashtul/Fix-ThreadSafeContext-functions-names
fix ThreadSafeContext lock/unlock function names
| -rw-r--r-- | src/module.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/module.c b/src/module.c index f37d987e0..8c61f60e2 100644 --- a/src/module.c +++ b/src/module.c @@ -4740,9 +4740,9 @@ int RM_BlockedClientDisconnected(RedisModuleCtx *ctx) { * * To call non-reply APIs, the thread safe context must be prepared with: * - * RedisModule_ThreadSafeCallStart(ctx); + * RedisModule_ThreadSafeContextLock(ctx); * ... make your call here ... - * RedisModule_ThreadSafeCallStop(ctx); + * RedisModule_ThreadSafeContextUnlock(ctx); * * This is not needed when using `RedisModule_Reply*` functions, assuming * that a blocked client was used when the context was created, otherwise |