From: Nathan Chancellor <nathan@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Nathan Chancellor <nathan@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>, Yao Zi <me@ziyao.cc>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: tools: relocs: Ship a definition of R_MIPS_PC32
Date: Tue, 03 Feb 2026 11:53:06 -0700 [thread overview]
Message-ID: <177014478629.2310701.14623005254080630046.b4-ty@kernel.org> (raw)
In-Reply-To: <20260202041610.61389-1-me@ziyao.cc>
On Mon, 02 Feb 2026 04:16:10 +0000, Yao Zi wrote:
> R_MIPS_PC32 is a GNU extension, its definition is available in glibc
> only since 2.39 (released in 2024), and not available in musl libc yet.
> Provide our own definition for R_MIPS_PC32 and use it if necessary to
> fix relocs tool building on musl and older glibc systems.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next
Thanks!
[1/1] MIPS: tools: relocs: Ship a definition of R_MIPS_PC32
https://git.kernel.org/kbuild/c/87abe931fbc34
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2026-02-03 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 4:16 Yao Zi
2026-02-02 9:17 ` Ard Biesheuvel
2026-02-02 23:07 ` Nathan Chancellor
2026-02-03 3:56 ` Yao Zi
2026-02-03 12:31 ` Ard Biesheuvel
2026-02-05 1:26 ` Maciej W. Rozycki
2026-02-05 8:26 ` Yao Zi
2026-02-05 8:39 ` Ard Biesheuvel
2026-02-03 18:53 ` Nathan Chancellor [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=177014478629.2310701.14623005254080630046.b4-ty@kernel.org \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=me@ziyao.cc \
--cc=tsbogend@alpha.franken.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
all inboxes | Powered by JetHome®