public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: HeeSu Kim <mlksvender@gmail.com>
To: ojeda@kernel.org
Cc: charmitro@posteo.net, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64
Date: Tue,  3 Feb 2026 08:39:00 +0900	[thread overview]
Message-ID: <20260202233900.2699668-1-mlksvender@gmail.com> (raw)
In-Reply-To: <CANiq72kFFFB6k8D9TeSe2hFG3e6AhCqWTMVJXkKyLc8F=TFhbg@mail.gmail.com>

On Tue, Feb 03, 2026, Miguel Ojeda wrote:
> Could you please elaborate on the issues you are seeing, e.g. how to
> reproduce them?
>
> The flag is only used to silence errors from checks that were added to
> `rustc` and it is ignored otherwise (that is why the workaround was
> written like that).

After reviewing my build logs, I found that the error I encountered was
"unknown codegen option: -Cunsafe-allow-abi-mismatch" because I was
using rustc 1.85 at the time. The flag was added in rustc 1.88.

So this was not an architecture-specific issue. I apologize for the
confusion and would like to withdraw this patch.

Best regards,
HeeSu Kim

       reply	other threads:[~2026-02-02 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANiq72kFFFB6k8D9TeSe2hFG3e6AhCqWTMVJXkKyLc8F=TFhbg@mail.gmail.com>
2026-02-02 23:39 ` HeeSu Kim [this message]
2026-02-02 14:41   ` [PATCH] rust: Makefile: apply fixed-x18 workaround only on arm64 Miguel Ojeda
2026-02-02 22:21 HeeSu Kim
2026-02-02 13:59 ` Charalampos Mitrodimas
2026-02-02 23:17   ` HeeSu Kim
2026-02-02 14:20 ` Miguel Ojeda
2026-02-02 14:24 ` Gary Guo
2026-02-02 23:45   ` HeeSu Kim

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=20260202233900.2699668-1-mlksvender@gmail.com \
    --to=mlksvender@gmail.com \
    --cc=charmitro@posteo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@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