From: "tip-bot2 for Borislav Petkov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Borislav Petkov <bp@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/sgx] x86/sgx: Fix sgx_ioc_enclave_provision() kernel-doc comment
Date: Tue, 24 Nov 2020 10:34:55 -0000 [thread overview]
Message-ID: <160621409509.11115.5086990104401029239.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20201123181922.0c009406@canb.auug.org.au>
The following commit has been merged into the x86/sgx branch of tip:
Commit-ID: afe76eca862ccde2a0c30105fc97a46a0b59339b
Gitweb: https://git.kernel.org/tip/afe76eca862ccde2a0c30105fc97a46a0b59339b
Author: Borislav Petkov <bp@suse.de>
AuthorDate: Mon, 23 Nov 2020 11:11:17 +01:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Tue, 24 Nov 2020 10:46:01 +01:00
x86/sgx: Fix sgx_ioc_enclave_provision() kernel-doc comment
Fix
./arch/x86/kernel/cpu/sgx/ioctl.c:666: warning: Function parameter or member \
'encl' not described in 'sgx_ioc_enclave_provision'
./arch/x86/kernel/cpu/sgx/ioctl.c:666: warning: Excess function parameter \
'enclave' description in 'sgx_ioc_enclave_provision'
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/20201123181922.0c009406@canb.auug.org.au
---
arch/x86/kernel/cpu/sgx/ioctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/sgx/ioctl.c b/arch/x86/kernel/cpu/sgx/ioctl.c
index 30aefc9..c206aee 100644
--- a/arch/x86/kernel/cpu/sgx/ioctl.c
+++ b/arch/x86/kernel/cpu/sgx/ioctl.c
@@ -652,7 +652,7 @@ out:
/**
* sgx_ioc_enclave_provision() - handler for %SGX_IOC_ENCLAVE_PROVISION
- * @enclave: an enclave pointer
+ * @encl: an enclave pointer
* @arg: userspace pointer to a struct sgx_enclave_provision instance
*
* Allow ATTRIBUTE.PROVISION_KEY for an enclave by providing a file handle to
prev parent reply other threads:[~2020-11-24 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 7:19 linux-next: build warnings after merge of the tip tree Stephen Rothwell
2020-11-23 10:13 ` [PATCH] x86/sgx: Fix sgx_ioc_enclave_provision() kernel-doc comment Borislav Petkov
2020-11-23 23:03 ` linux-next: build warnings after merge of the tip tree Jarkko Sakkinen
2020-11-24 10:34 ` tip-bot2 for Borislav Petkov [this message]
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=160621409509.11115.5086990104401029239.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.org \
/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).