mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nsc@kernel.org>,  Brian Cain <bcain@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-hexagon@vger.kernel.org,
	"Thomas Weißschuh" <linux@weissschuh.net>
Subject: [PATCH 9/9] kbuild: uapi: remove now unneeded guard headers
Date: Fri, 27 Feb 2026 07:38:07 +0100	[thread overview]
Message-ID: <20260227-kbuild-uapi-libc-v1-9-c17de0d19776@weissschuh.net> (raw)
In-Reply-To: <20260227-kbuild-uapi-libc-v1-0-c17de0d19776@weissschuh.net>

The test compilation does not allow usage of the toolchain headers
anymore, so these dummy headers are not needed anymore.

Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
---
 usr/dummy-include/stdbool.h | 7 -------
 usr/dummy-include/stdlib.h  | 7 -------
 2 files changed, 14 deletions(-)

diff --git a/usr/dummy-include/stdbool.h b/usr/dummy-include/stdbool.h
deleted file mode 100644
index 54ff9e9c90ac..000000000000
--- a/usr/dummy-include/stdbool.h
+++ /dev/null
@@ -1,7 +0,0 @@
-/* SPDX-License-Identifier: GPL-2.0-only */
-#ifndef _STDBOOL_H
-#define _STDBOOL_H
-
-#error "Please do not include <stdbool.h> from exported headers"
-
-#endif /* _STDBOOL_H */
diff --git a/usr/dummy-include/stdlib.h b/usr/dummy-include/stdlib.h
deleted file mode 100644
index e8c21888e371..000000000000
--- a/usr/dummy-include/stdlib.h
+++ /dev/null
@@ -1,7 +0,0 @@
-/* SPDX-License-Identifier: GPL-2.0-only */
-#ifndef _STDLIB_H
-#define _STDLIB_H
-
-#error "Please do not include <stdlib.h> from exported headers"
-
-#endif /* _STDLIB_H */

-- 
2.53.0


  parent reply	other threads:[~2026-02-27  6:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:37 [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers Thomas Weißschuh
2026-02-27  6:37 ` [PATCH 1/9] hexagon: uapi: Fix structure alignment attribute Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 2/9] kbuild: uapi: test linux/bpf_perf_event.h on powerpc Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 3/9] kbuild: uapi: deduplicate linux/bpf_perf_event.h exclusions Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 4/9] kbuild: uapi: completely exclude linux/bpf_perf_event.h on nios2 Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 5/9] kbuild: uapi: only use dummy-include for headers which use libc Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 6/9] kbuild: uapi: provide stub includes for some libc headers Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 7/9] kbuild: uapi: use custom stub headers instead of libc ones Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 8/9] kbuild: uapi: simplify libc dependency logic Thomas Weißschuh
2026-02-27  6:38 ` Thomas Weißschuh [this message]
2026-02-27  9:18 ` [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers Arnd Bergmann
2026-02-27  9:38   ` Thomas Weißschuh
2026-02-27 10:04     ` Arnd Bergmann
2026-03-05  9:41 ` Nicolas Schier
2026-03-10  1:00 ` Nathan Chancellor
2026-03-12 12:08 ` Nicolas Schier

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=20260227-kbuild-uapi-libc-v1-9-c17de0d19776@weissschuh.net \
    --to=linux@weissschuh.net \
    --cc=arnd@arndb.de \
    --cc=bcain@kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@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

all inboxes | Powered by JetHome®