linux-kernel - Re: [GIT PULL] Immutable branch between MFD, Char and Crypto due for the v6.18 merge window

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: <20250917171232.GA1457869@ax162>
Date: Wed, 17 Sep 2025 10:12:32 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Lee Jones <lee@...nel.org>
Cc: Qunqin Zhao <zhaoqunqin@...ngson.cn>, herbert@...dor.apana.org.au,
	jarkko@...nel.org, linux-kernel@...r.kernel.org,
	loongarch@...ts.linux.dev, davem@...emloft.net,
	linux-crypto@...r.kernel.org, peterhuewe@....de, jgg@...pe.ca,
	linux-integrity@...r.kernel.org, sgarzare@...hat.com
Subject: Re: [GIT PULL] Immutable branch between MFD, Char and Crypto due for
 the v6.18 merge window

On Wed, Sep 17, 2025 at 10:38:23AM +0100, Lee Jones wrote:
> Ah, gotcha.  I thought you were saying that 07d8004d6fb9 ("tpm: add
> bufsiz parameter in the .send callback") was applied somewhere else.  In
> which case, I need to figure out why my build testing didn't catch it.

Maybe because this driver ultimately depends on CONFIG_LOONGARCH (i.e.,
no COMPILE_TEST)? I would argue most people don't do LoongArch builds.

> I'd be happy with a formal patch from you or I can create the patch and
> add your {Reported,Suggested}-by.  How would you like to proceed?

I sent a formal patch to make life a little easier for you :)

https://lore.kernel.org/20250917-tpm-loongson-add-bufsiz-v1-1-972a75c0aab2@kernel.org/

Cheers,
Nathan