linux-kernel - Re: [PATCH v7 2/2] MIPS: Move r4k

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAAhV-H4q3bki+_SwRq9JW2LwS6ny+N1eS-UJsZ5N2vtZRVWHeA@mail.gmail.com>
Date: Wed, 30 Apr 2025 11:15:48 +0800
From: Huacai Chen <chenhuacai@...nel.org>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc: Marco Crivellari <marco.crivellari@...e.com>, "Maciej W. Rozycki" <macro@...am.me.uk>, 
	linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Frederic Weisbecker <frederic@...nel.org>, Anna-Maria Behnsen <anna-maria@...utronix.de>, 
	Thomas Gleixner <tglx@...utronix.de>, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v7 2/2] MIPS: Move r4k_wait() to .cpuidle.text section

On Mon, Apr 28, 2025 at 6:24 PM Thomas Bogendoerfer
<tsbogend@...ha.franken.de> wrote:
>
> On Mon, Apr 28, 2025 at 12:20:31PM +0200, Marco Crivellari wrote:
> > Hi,
> >
> > If it sounds good also to Maciej, I will submit the new version with the
> > space before "ax" (and of course, the ".previous").
>
> save your time, this is already applied and I won't rebase the branch
> just because of this minor bisection problem.
But this series lacks a tested-by from Jiaxun Yang. The first patch is
so complicated because it should handle the pre MIPS III case, I have
no old MIPS hardware, Jiaxun said he has [1] but he hasn't tested it
by now.

[1] https://lore.kernel.org/linux-mips/20250315194002.13778-1-marco.crivellari@suse.com/T/#m632ac91077d4cbc750b8acaacef08cad8bfd29da

Huacai

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