From: Xi Ruoyao <xry111@xry111.site>
To: Guo Ren <guoren@kernel.org>, Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Palmer Dabbelt <palmer@dabbelt.com>, Fangrui Song <i@maskray.me>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-csky@vger.kernel.org, loongarch@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Ping: [PATCH 0/3] Drop explicit --hash-style= setting for new
Date: Wed, 05 Mar 2025 21:27:04 +0800 [thread overview]
Message-ID: <91797ac4bbe27d7d60b89053050e429bcd630db3.camel@xry111.site> (raw)
In-Reply-To: <20250224112042.60282-1-xry111@xry111.site>
Ping.
On Mon, 2025-02-24 at 19:20 +0800, Xi Ruoyao wrote:
> For riscv, csky, and LoongArch, GNU hash had already become the de-
> facto
> standard when they borned, so there's no Glibc/Musl releases for them
> without GNU hash support, and the traditional SysV hash is just
> wasting
> space for them.
>
> Remove those settings and follow the distro toolchain default, which
> is
> likely --hash-style=gnu. In the past it could break vDSO self tests,
> but now the issue has been addressed by commit
> e0746bde6f82 ("selftests/vDSO: support DT_GNU_HASH").
>
> Xi Ruoyao (3):
> riscv: vDSO: Remove --hash-style=both
> csky: vDSO: Remove --hash-style=both
> LoongArch: vDSO: Remove --hash-style=sysv
>
> arch/csky/kernel/vdso/Makefile | 2 +-
> arch/loongarch/vdso/Makefile | 2 +-
> arch/riscv/kernel/vdso/Makefile | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2025-03-05 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 11:20 Xi Ruoyao
2025-02-24 11:20 ` [PATCH 1/3] riscv: vDSO: Remove --hash-style=both Xi Ruoyao
2025-02-24 11:20 ` [PATCH 2/3] csky: " Xi Ruoyao
2025-02-24 11:20 ` [PATCH 3/3] LoongArch: vDSO: Remove --hash-style=sysv Xi Ruoyao
2025-03-30 9:55 ` Huacai Chen
2025-03-05 13:27 ` Xi Ruoyao [this message]
2025-03-10 2:13 ` Ping: [PATCH 0/3] Drop explicit --hash-style= setting for new Guo Ren
2025-03-30 12:18 ` Xi Ruoyao
2025-05-09 17:30 ` patchwork-bot+linux-riscv
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=91797ac4bbe27d7d60b89053050e429bcd630db3.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=guoren@kernel.org \
--cc=i@maskray.me \
--cc=kernel@xen0n.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=loongarch@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=yangtiezhu@loongson.cn \
/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®