linux-kernel - Re: [PATCH 1/3] soc cache: L3 cache driver for HiSilicon SoC

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <e59c7556-d001-4a34-8db3-127dc25f3897@kernel.org>
Date: Thu, 5 Feb 2026 10:37:11 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Arnd Bergmann <arnd@...db.de>, Yushan Wang <wangyushan12@...wei.com>,
 Alexandre Belloni <alexandre.belloni@...tlin.com>,
 Drew Fustini <fustini@...nel.org>,
 Jonathan Cameron <Jonathan.Cameron@...wei.com>,
 Linus Walleij <linus.walleij@...aro.org>, Will Deacon <will@...nel.org>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: fanghao11@...wei.com, linuxarm@...wei.com, liuyonglong@...wei.com,
 prime.zeng@...ilicon.com, Zhou Wang <wangzhou1@...ilicon.com>,
 Wei Xu <xuwei5@...ilicon.com>
Subject: Re: [PATCH 1/3] soc cache: L3 cache driver for HiSilicon SoC

On 03/02/2026 18:19, Arnd Bergmann wrote:
> On Tue, Feb 3, 2026, at 17:18, Yushan Wang wrote:
>> The driver will create a file of `/dev/hisi_l3c` on init, mmap
>> operations to it will allocate a memory region that is guaranteed to be
>> placed in L3 cache.
>>
>> The driver also provides unmap() to deallocated the locked memory.
>>
>> The driver also provides an ioctl interface for user to get cache lock
>> information, such as lock restrictions and locked sizes.
>>
>> Signed-off-by: Yushan Wang <wangyushan12@...wei.com>
> 
> Hi Yushan,
> 
> Thanks for your submission. Since we are in the last week of
> the merge window, this is not going to be linux-7.0 material,
> but I'll have a quick look for now.


To be clear - this is a v3 but with removed previous history...

Previous version:
https://lore.kernel.org/all/20251217102357.1730573-2-wangyushan12@huawei.com/

Or even v4?

https://lore.kernel.org/all/20250122065803.3363926-2-wangyushan12@huawei.com/

Yushan, please start versioning your patches correctly. Use b4 or git
format-patch -vx

Otherwise, please explain us how can we compare it with `b4 diff` with
previous version?

Sending something AGAIN as v1 ignoring entire previous submission is
clear no go. Like you are trying till it succeeds. Negative review?
Let's try from v1 this time...

This is not correct and it should not be my task to find your previous
discussions and decipher this v1.


Best regards,
Krzysztof