From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Borislav Petkov <bp@suse•de>
Cc: Sean Christopherson <seanjc@google•com>,
Cedric Xing <cedric.xing@intel•com>,
Jarkko Sakkinen <jarkko@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings in Linus' tree
Date: Thu, 6 Nov 2025 14:55:06 +1100 [thread overview]
Message-ID: <20251106145506.145fc620@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
Hi all,
Today's linux-next build (htmldocs) produced these warnings:
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'r8' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'r9' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'rdi' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'rdx' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'rsi' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:157 function parameter 'rsp' not described in 'sgx_enclave_user_handler_t'
WARNING: arch/x86/include/uapi/asm/sgx.h:17 Enum value 'SGX_PAGE_MEASURE' not described in enum 'sgx_page_flags'
WARNING: arch/x86/include/uapi/asm/sgx.h:184 struct member 'reserved' not described in 'sgx_enclave_run'
Introduced by commits
c6d26d370767 ("x86/sgx: Add SGX_IOC_ENCLAVE_ADD_PAGES")
846643695201 ("x86/vdso: Implement a vDSO for Intel SGX enclave call")
"make htmldocs" was not reporting all warnings for some time. This has
now been fixed and these appeared today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-11-06 3:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 3:55 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 4:16 linux-next: build warnings in Linus' tree Stephen Rothwell
2025-12-16 1:05 ` Stephen Rothwell
2025-12-16 3:14 ` Randy Dunlap
2024-05-28 3:30 Stephen Rothwell
2022-06-14 6:57 Stephen Rothwell
2022-05-26 7:21 Stephen Rothwell
2022-01-27 4:30 Stephen Rothwell
2022-01-27 6:01 ` Christoph Hellwig
2022-01-27 16:44 ` Stephen Rothwell
2022-01-27 4:24 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23 7:04 ` Borislav Petkov
2021-11-05 5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2021-10-08 5:47 Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-11 20:42 ` Rob Herring
2021-10-12 14:39 ` Arnd Bergmann
2021-10-13 22:12 ` Anatolij Gustschin
2021-10-13 22:17 ` Rob Herring
2021-10-13 22:28 ` Anatolij Gustschin
2021-10-13 23:22 ` Rob Herring
2021-10-14 8:44 ` Arnd Bergmann
2021-10-14 12:24 ` Anatolij Gustschin
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09 0:15 ` Stephen Rothwell
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31 ` Nicolas Saenz Julienne
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2013-07-04 4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2011-08-15 1:57 Stephen Rothwell
2011-05-23 1:25 Stephen Rothwell
2011-05-23 2:31 ` Eduardo Silva
2011-01-14 0:17 Stephen Rothwell
2011-01-14 0:09 Stephen Rothwell
2011-01-14 0:17 ` Andrew Morton
2011-01-14 1:06 ` Greg KH
2010-08-17 1:24 Stephen Rothwell
2010-08-30 1:42 ` Stephen Rothwell
2010-08-30 6:08 ` Zhang Rui
2010-09-03 2:01 ` Stephen Rothwell
2010-09-03 2:36 ` Len Brown
2010-09-17 4:26 ` Stephen Rothwell
2010-09-27 13:31 ` Stephen Rothwell
2010-08-07 2:21 Stephen Rothwell
2010-08-07 8:13 ` Vikas Chaudhary
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=20251106145506.145fc620@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bp@suse$(echo .)de \
--cc=cedric.xing@intel$(echo .)com \
--cc=jarkko@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=seanjc@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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