From ca3efd57c2c9c5bda236c63a3f8c64ba49d06e8d Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 28 Sep 2022 15:44:23 +0200 Subject: [PATCH] CURLSHOPT_UNLOCKFUNC.3: the callback as no 'access' argument Probably a copy and paste error from the lock function man page. Reported-by: Robby Simpson Fixes #9612 Closes #9613 --- docs/libcurl/opts/CURLSHOPT_UNLOCKFUNC.3 | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/libcurl/opts/CURLSHOPT_UNLOCKFUNC.3 b/docs/libcurl/opts/CURLSHOPT_UNLOCKFUNC.3 index 0a8a7aecfaf2..b46022128cae 100644 --- a/docs/libcurl/opts/CURLSHOPT_UNLOCKFUNC.3 +++ b/docs/libcurl/opts/CURLSHOPT_UNLOCKFUNC.3 @@ -45,8 +45,6 @@ is released. The \fIdata\fP argument tells what kind of data libcurl wants to unlock. Make sure that the callback uses a different lock for each kind of data. -\fIaccess\fP defines what access type libcurl wants, shared or single. - \fIuserptr\fP is the private pointer you set with \fICURLSHOPT_USERDATA\fP. This pointer is not used by libcurl itself. .SH PROTOCOLS