From: Masahiro Yamada <masahiroy@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH 5/6] kexec.h: add linux/kexec.h to UAPI compile-test coverage
Date: Thu, 10 Feb 2022 11:11:28 +0900 [thread overview]
Message-ID: <20220210021129.3386083-6-masahiroy@kernel.org> (raw)
In-Reply-To: <20220210021129.3386083-1-masahiroy@kernel.org>
linux/kexec.h is currently excluded from the UAPI compile-test because
of the errors like follows:
HDRTEST usr/include/linux/kexec.h
In file included from <command-line>:
./usr/include/linux/kexec.h:56:9: error: unknown type name ‘size_t’
56 | size_t bufsz;
| ^~~~~~
./usr/include/linux/kexec.h:58:9: error: unknown type name ‘size_t’
58 | size_t memsz;
| ^~~~~~
The errors can be fixed by replacing size_t with __kernel_size_t.
Then, remove the no-header-test entry from user/include/Makefile.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
include/uapi/linux/kexec.h | 4 ++--
usr/include/Makefile | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/include/uapi/linux/kexec.h b/include/uapi/linux/kexec.h
index 778dc191c265..fb7e2ef60825 100644
--- a/include/uapi/linux/kexec.h
+++ b/include/uapi/linux/kexec.h
@@ -54,9 +54,9 @@
*/
struct kexec_segment {
const void *buf;
- size_t bufsz;
+ __kernel_size_t bufsz;
const void *mem;
- size_t memsz;
+ __kernel_size_t memsz;
};
#endif /* __KERNEL__ */
diff --git a/usr/include/Makefile b/usr/include/Makefile
index 9e35d022fd88..48bb789099d5 100644
--- a/usr/include/Makefile
+++ b/usr/include/Makefile
@@ -31,7 +31,6 @@ no-header-test += linux/cyclades.h
no-header-test += linux/errqueue.h
no-header-test += linux/hdlc/ioctl.h
no-header-test += linux/ivtv.h
-no-header-test += linux/kexec.h
no-header-test += linux/matroxfb.h
no-header-test += linux/omap3isp.h
no-header-test += linux/omapfb.h
--
2.32.0
next prev parent reply other threads:[~2022-02-10 2:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 2:11 [PATCH 0/6] Add more export headers to compile-test coverage Masahiro Yamada
2022-02-10 2:11 ` [PATCH 1/6] signal.h: add linux/signal.h and asm/signal.h to UAPI " Masahiro Yamada
2022-02-10 9:43 ` Arnd Bergmann
2022-02-10 12:45 ` Geert Uytterhoeven
2022-03-13 10:28 ` Dmitry V. Levin
2022-02-10 2:11 ` [PATCH 2/6] shmbuf.h: add asm/shmbuf.h " Masahiro Yamada
2022-02-10 9:39 ` Arnd Bergmann
2022-03-13 10:29 ` Dmitry V. Levin
2022-02-10 2:11 ` [PATCH 3/6] android/binder.h: add linux/android/binder(fs).h " Masahiro Yamada
2022-02-10 9:37 ` Arnd Bergmann
2022-02-10 2:11 ` [PATCH 4/6] fsmap.h: add linux/fsmap.h " Masahiro Yamada
2022-02-10 9:42 ` Arnd Bergmann
2022-02-10 2:11 ` Masahiro Yamada [this message]
2022-02-10 9:41 ` [PATCH 5/6] kexec.h: add linux/kexec.h " Arnd Bergmann
2022-02-10 2:11 ` [PATCH 6/6] reiserfs_xattr.h: add linux/reiserfs_xattr.h " Masahiro Yamada
2022-02-10 9:40 ` Arnd Bergmann
2022-02-10 9:45 ` [PATCH 0/6] Add more export headers to " Arnd Bergmann
2022-02-11 5:23 ` Masahiro Yamada
2022-02-17 8:15 ` Arnd Bergmann
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=20220210021129.3386083-6-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.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).