From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Jonathan Corbet" <corbet@lwn.net>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org,
x86@kernel.org
Subject: [PATCH 1/2] asm: sgx.h: fix a typo on a kernel-doc markup
Date: Wed, 2 Dec 2020 09:27:14 +0100 [thread overview]
Message-ID: <ca11a4540d981cbd5f026b6cbc8931aa55654e00.1606897462.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1606897462.git.mchehab+huawei@kernel.org>
As warned by kernel-doc:
arch/x86/include/uapi/asm/sgx.h:19: warning: expecting prototype for enum sgx_epage_flags. Prototype was for enum sgx_page_flags instead
There is a typo at the kernel-doc markup:
sgx_epage_flags -> sgx_page_flags
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
arch/x86/include/uapi/asm/sgx.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/uapi/asm/sgx.h b/arch/x86/include/uapi/asm/sgx.h
index 791e45334a4a..9034f3007c4e 100644
--- a/arch/x86/include/uapi/asm/sgx.h
+++ b/arch/x86/include/uapi/asm/sgx.h
@@ -9,7 +9,7 @@
#include <linux/ioctl.h>
/**
- * enum sgx_epage_flags - page control flags
+ * enum sgx_page_flags - page control flags
* %SGX_PAGE_MEASURE: Measure the page contents with a sequence of
* ENCLS[EEXTEND] operations.
*/
--
2.28.0
next prev parent reply other threads:[~2020-12-02 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 8:27 [PATCH 0/2] Fix some kernel-doc markups with wrong identifiers Mauro Carvalho Chehab
2020-12-02 8:27 ` Mauro Carvalho Chehab [this message]
2020-12-02 10:07 ` [PATCH 1/2] asm: sgx.h: fix a typo on a kernel-doc markup Borislav Petkov
2020-12-02 16:24 ` Jarkko Sakkinen
2020-12-02 8:27 ` [PATCH 2/2] drm: amdgpu: fix " Mauro Carvalho Chehab
2020-12-02 8:45 ` Christian König
2020-12-03 5:01 ` Alex Deucher
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=ca11a4540d981cbd5f026b6cbc8931aa55654e00.1606897462.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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).