From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nicolas Schier <nicolas.schier@linux.dev>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH 0/2] kbuild: userprogs: also inherit byte order and ABI from kernel
Date: Thu, 14 Aug 2025 11:46:46 -0700 [thread overview]
Message-ID: <20250814184646.GA1764877@ax162> (raw)
In-Reply-To: <20250813-kbuild-userprogs-bits-v1-0-2d9f7f411083@linutronix.de>
On Wed, Aug 13, 2025 at 07:43:39AM +0200, Thomas Weißschuh wrote:
> Make sure the byte order and ABI of the userprogs matches the one of the
> kernel, similar to how the bit size is handled.
> Otherwise the userprogs may not be executable.
> This happens for example on powerpc little endian, or riscv32.
>
> These patches where originally part of my series "kunit: Introduce UAPI
> testing framework" [0], but that isn't going anywhere right now and the
> patches are useful on their own.
>
> [0] kunit: Introduce UAPI testing framework
> ---
> Thomas Weißschuh (2):
> kbuild: userprogs: avoid duplication of flags inherited from kernel
> kbuild: userprogs: also inherit byte order and ABI from kernel
Seems reasonable to me. Should I fast track this via kbuild-fixes or
should I just apply it to kbuild-next? I am guessing you only noticed
this in the context of developing [0] so it might not be a big issue in
the wild?
Cheers,
Nathan
next prev parent reply other threads:[~2025-08-14 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 5:43 [PATCH 0/2] kbuild: userprogs: also inherit byte order and ABI from kernel Thomas Weißschuh
2025-08-13 5:43 ` [PATCH 1/2] kbuild: userprogs: avoid duplication of flags inherited " Thomas Weißschuh
2025-08-13 5:43 ` [PATCH 2/2] kbuild: userprogs: also inherit byte order and ABI " Thomas Weißschuh
2025-08-27 6:31 ` Thomas Weißschuh
2025-08-27 22:49 ` Nathan Chancellor
2025-09-01 9:51 ` Thomas Weißschuh
2025-09-03 22:31 ` Nathan Chancellor
2025-09-07 5:24 ` Nicolas Schier
2025-09-09 5:50 ` Thomas Weißschuh
2025-10-02 13:23 ` Thomas Weißschuh
2025-10-04 19:17 ` Nicolas Schier
2025-10-06 19:13 ` Nathan Chancellor
2025-08-14 18:46 ` Nathan Chancellor [this message]
2025-08-15 5:57 ` [PATCH 0/2] " Thomas Weißschuh
2025-08-15 21:16 ` Nathan Chancellor
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=20250814184646.GA1764877@ax162 \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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.