From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from canpmsgout02.his.huawei.com (canpmsgout02.his.huawei.com [113.46.200.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 91A6913C918 for ; Thu, 5 Feb 2026 11:19:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=113.46.200.217 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770290360; cv=none; b=QqbnO0a9nBWcwpeYgzW9iPaHms1aPjpAgoZDGiLT5Xem3pizewXQZex4HGm1Im//pFO7yOco0/W8QH/3WymM9gUh4ySBzCQRcQzfy43FGGvKgVXlXhBeW1aZgNxBmQZlMe81SmDDXkvkjcEarw6iYPhgU90TqIPTPTGR6PbXoDo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770290360; c=relaxed/simple; bh=gtBNeFmth+hB0BG4YYb6qWCV78JJBEFBO6LnaUUXrtg=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=gKz8Fns1sUS0KDTAH6qiSj4OliP0oCcfmXZPw7P4kruIjAEyCMBp4MeH38nniit62cV/q9z+fbCpb9LyVJUTym/gdJmlDk/ZXbyb18Tcz2YAP0gDi4T2nYs2cbefLSBapHzrWy9b2WkbzMV0xZNge3Fa88bscZSzvdAvdzen1Oo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; dkim=pass (1024-bit key) header.d=huawei.com header.i=@huawei.com header.b=wezTHypd; arc=none smtp.client-ip=113.46.200.217 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=huawei.com header.i=@huawei.com header.b="wezTHypd" dkim-signature: v=1; a=rsa-sha256; d=huawei.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From; bh=gtBNeFmth+hB0BG4YYb6qWCV78JJBEFBO6LnaUUXrtg=; b=wezTHypdGHmKi7XbrrQSKmKK4c5Y+Ns8Vkyz2hYgRuGyiPRWe/UdG9Qe6iBEdLegFHMigvfQN qMojRzjjc2POrUkSGn4XxrQYf0WlzjGhViRXe+ZPOq2auItgmTxFerdgiX0xOBipiScZyzB1je6 lC5ta9UXYBRMTczjK696UHk= Received: from mail.maildlp.com (unknown [172.19.162.223]) by canpmsgout02.his.huawei.com (SkyGuard) with ESMTPS id 4f6F4D4nY6zcZym; Thu, 5 Feb 2026 19:14:52 +0800 (CST) Received: from dggemv705-chm.china.huawei.com (unknown [10.3.19.32]) by mail.maildlp.com (Postfix) with ESMTPS id 3044B40569; Thu, 5 Feb 2026 19:19:17 +0800 (CST) Received: from kwepemn100008.china.huawei.com (7.202.194.111) by dggemv705-chm.china.huawei.com (10.3.19.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 5 Feb 2026 19:19:17 +0800 Received: from [10.67.120.139] (10.67.120.139) by kwepemn100008.china.huawei.com (7.202.194.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Thu, 5 Feb 2026 19:19:16 +0800 Message-ID: <1d7abd11-2064-4437-8ad7-7cfe1b2e75c0@huawei.com> Date: Thu, 5 Feb 2026 19:19:15 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 1/3] soc cache: L3 cache driver for HiSilicon SoC To: Krzysztof Kozlowski CC: Arnd Bergmann , Alexandre Belloni , Drew Fustini , "Jonathan Cameron" , Linus Walleij , Will Deacon , , , , , , , Zhou Wang , Wei Xu , Yushan Wang References: <20260203161843.649417-1-wangyushan12@huawei.com> <20260203161843.649417-2-wangyushan12@huawei.com> Content-Language: en-US From: wangyushan In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-ClientProxiedBy: kwepems100001.china.huawei.com (7.221.188.238) To kwepemn100008.china.huawei.com (7.202.194.111) On 2/5/2026 5:37 PM, Krzysztof Kozlowski wrote: > 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 >> >> 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 Hi Krzysztof, Sorry about the confusing versions, the complete history is as below: Link to v1: https://lore.kernel.org/all/20250107132907.3521574-1-wangyushan12@huawei.com Link to v2: https://lore.kernel.org/all/20250122065803.3363926-1-wangyushan12@huawei.com/ Link to RFC v1: https://lore.kernel.org/all/20251125080542.3721829-1-wangyushan12@huawei.com/ Link to RFC v2: https://lore.kernel.org/all/20251217102357.1730573-1-wangyushan12@huawei.com/ Link to v1 again (this message): https://lore.kernel.org/all/20260203161843.649417-1-wangyushan12@huawei.com/ > > 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. I did spin 2 versions to mainline as the actual v1, the thread was quiet. Then I made a major refactor to it and sent it as RFC, the thread went quiet again but some compile check issues popped up. I spinned 2 versions of RFC for the compile issues and removed RFC in this version since no strong objection showed up. Apologize that I broke the rules and any inconvenience caused by it. As there's little discussion in previous patches, is it OK that we start here as v1? Anyway I will include the whole history in the coverletter to prevent more confusion. > > > Best regards, > Krzysztof > Thanks, Yushan