From: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org,
Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Subject: [patch] keyctl.2: declare auth_key
Date: Fri, 12 Jun 2020 17:35:33 +0200 [thread overview]
Message-ID: <20200612153533.23783-1-open.source@oleksandr-kravchuk.com> (raw)
The variable is used in the code example, but not declared, leading to
an expected compilation error:
`error: ‘auth_key’ undeclared (first use in this function)`.
Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
---
man2/keyctl.2 | 1 +
1 file changed, 1 insertion(+)
diff --git a/man2/keyctl.2 b/man2/keyctl.2
index 3dea4266c..08ae92d6d 100644
--- a/man2/keyctl.2
+++ b/man2/keyctl.2
@@ -2103,6 +2103,7 @@ main(int argc, char *argv[])
char dbuf[256];
char auth_key_payload[256];
int akp_size; /* Size of auth_key_payload */
+ int auth_key;
fp = fopen("/tmp/key_instantiate.log", "w");
if (fp == NULL)
--
2.17.1
next reply other threads:[~2020-06-12 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 15:35 Oleksandr Kravchuk [this message]
2020-06-19 12:50 ` [patch] keyctl.2: declare auth_key Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200612153533.23783-1-open.source@oleksandr-kravchuk.com \
--to=open.source@oleksandr-kravchuk.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).