public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Implement ARCH_HAS_CC_CAN_LINK
Date: Mon, 9 Feb 2026 12:59:36 +0100	[thread overview]
Message-ID: <aYnMKFmB3Ve5-2OS@alpha.franken.de> (raw)
In-Reply-To: <20260109-cc-can-link-mips-v2-1-38123bfc5628@linutronix.de>

On Fri, Jan 09, 2026 at 11:08:49AM +0100, Thomas Weißschuh wrote:
> The generic CC_CAN_LINK detection does not handle different byte orders
> or ABIs. This may lead to userprogs which are not actually runnable on
> the target kernel.
> 
> Use architecture-specific logic supporting byte orders instead.
> 
> Modern 64-bit toolchains default to a n32 libc, which are not
> supported by all kernel configurations, as MIPS32_N32 is optional.
> On 64-bit, test for a n32 ABI libc first and fall back to o64 and
> o32 if necessary.
> 
> Link: https://lore.kernel.org/lkml/20260105100507-14db55e3-aa71-48bf-a6ac-33b186bd082f@linutronix.de/
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> Changes in v2:
> - Use -mabi= over -m32/-m64
> - Link to v1: https://lore.kernel.org/r/20251222-cc-can-link-mips-v1-1-6d87a8afe442@linutronix.de
> ---
>  arch/mips/Kconfig | 28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)

applied to mips-next
Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2026-02-09 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 10:08 [PATCH v2] MIPS: Implement ARCH_HAS_CC_CAN_LINK Thomas Weißschuh
2026-02-09 11:59 ` Thomas Bogendoerfer [this message]

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=aYnMKFmB3Ve5-2OS@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox