All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	"Dodji Seketeli" <dodji@seketeli.org>,
	"John Moon" <john@jmoon.dev>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nsc@kernel.org>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	libabigail@sourceware.org
Subject: [PATCH 0/3] check-uapi: improve portability for testing headers
Date: Fri,  6 Mar 2026 17:33:06 +0100	[thread overview]
Message-ID: <20260306163309.2015837-1-arnd@kernel.org> (raw)

From: Arnd Bergmann <arnd@arndb.de>

While working on a series to clean up some uapi headers, I needed
to check the that the actual ABI remains unchanged. I found that
scripts/check-uapi.sh works well enough for architectures that have a
full toolchain installed, but not with the nolibc compilers I provide
on kernel.org.

I ended up with a series addressing three separate issues here, but in
the end I can now validate ABI changes across all supported architectures
and ABIs.

The third patch depends on a series from Thomas Weißschuh that was
just merged into the kbuild-for-next tree, the other ones could
also apply to older kernels. I have marked the second patch for
backports to stable kernels, this one is what caused me the most
work in debugging.

    Arnd

Arnd Bergmann (3):
  check-uapi: link into shared objects
  check-uapi: honor ${CROSS_COMPILE} setting
  check-uapi: use dummy libc includes

 scripts/check-uapi.sh | 19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)

-- 
2.39.5
Cc: Dodji Seketeli <dodji@seketeli.org>
Cc: John Moon <john@jmoon.dev>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Nicolas Schier <nsc@kernel.org>
Cc: Thomas Weißschuh <linux@weissschuh.net>
Cc: libabigail@sourceware.org
Cc: linux-kbuild@vger.kernel.org



             reply	other threads:[~2026-03-06 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:33 Arnd Bergmann [this message]
2026-03-06 16:33 ` [PATCH 1/3] check-uapi: link into shared objects Arnd Bergmann
2026-03-06 16:33 ` [PATCH 2/3] check-uapi: honor ${CROSS_COMPILE} setting Arnd Bergmann
2026-03-06 16:33 ` [PATCH 3/3] check-uapi: use dummy libc includes Arnd Bergmann
2026-03-06 16:39   ` Thomas Weißschuh
2026-03-06 16:45     ` Arnd Bergmann
2026-03-07  8:51       ` Thomas Weißschuh
2026-03-20 20:12         ` Nicolas Schier
2026-03-20 20:31           ` Thomas Weißschuh
2026-03-20 20:39             ` Nicolas Schier
2026-03-10  1:12 ` [PATCH 0/3] check-uapi: improve portability for testing headers Nathan Chancellor
2026-03-20 20:51 ` 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=20260306163309.2015837-1-arnd@kernel.org \
    --to=arnd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dodji@seketeli.org \
    --cc=john@jmoon.dev \
    --cc=libabigail@sourceware.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.