linux-kernel - Re: [PATCH] loongarch: Use '.ascii' instead of '.string' in __BUGVERBOSE

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: <20250701122224.GA1879931@ax162>
Date: Tue, 1 Jul 2025 05:22:24 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Huacai Chen <chenhuacai@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>, WANG Xuerui <kernel@...0n.name>,
	Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
	Bill Wendling <morbo@...gle.com>,
	Justin Stitt <justinstitt@...gle.com>, loongarch@...ts.linux.dev,
	linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] loongarch: Use '.ascii' instead of '.string' in
 __BUGVERBOSE_LOCATION

On Sun, Jun 29, 2025 at 11:59:57AM +0800, Huacai Chen wrote:
> On Tue, Jun 17, 2025 at 7:23 AM Nathan Chancellor <nathan@...nel.org> wrote:
> > Fixes: 5d476f66e6ad ("bugs/LoongArch: Concatenate 'cond_str' with '__FILE__' in __BUG_ENTRY(), to extend WARN_ON/BUG_ON output")
> 
> 5d476f66e6ad is not in upstream, so I prefer squash this patch to 5d476f66e6ad.

Sure, that's fine with me, assuming Ingo is fine with rebasing that
branch. I just want my builds back to green :)

Cheers,
Nathan