From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [45.249.212.190]) (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 5E0621E507 for ; Sat, 4 Jan 2025 10:28:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.190 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735986521; cv=none; b=TrHPdzmVSAS3KGgCnLdEaO1LjHYHox8p/Dwo+4YxFvyWJo6Na/jv0q78Gkl6+2erZUy3mcVkJUbGs9jQ+cMLBzhwANUQzZNF+my8VrtGsCejAnpZDIsplc7b2h326y10M9op+gBBglmonIXpSRuLlqNnpgrlT0XxVbJnKyrIxR8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1735986521; c=relaxed/simple; bh=A6gA1TH6UX3EMYTvmavn2NvVtjjc8p+otbBjobTjhI4=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=mhVV6W4HXvsJkUT0soolQGnazU/B1OkIB1KeMpew+3sJX0X8xxEuFg+/z94SW/G7iwdo1YtCwtu3CxV5thlsKTmkS7NpowFEvN4fX7N1cCLbF3cGGKsp7EwDEpxuwv1tGgcXI5XJfogRGl6gBdpmnN8lNN40cVinzPTm7rX18pQ= 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; arc=none smtp.client-ip=45.249.212.190 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 Received: from mail.maildlp.com (unknown [172.19.162.112]) by szxga04-in.huawei.com (SkyGuard) with ESMTP id 4YQGmg14MVz2DjkX; Sat, 4 Jan 2025 18:25:39 +0800 (CST) Received: from kwepemf100008.china.huawei.com (unknown [7.202.181.222]) by mail.maildlp.com (Postfix) with ESMTPS id 704A81402C7; Sat, 4 Jan 2025 18:28:35 +0800 (CST) Received: from [10.174.179.163] (10.174.179.163) by kwepemf100008.china.huawei.com (7.202.181.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Sat, 4 Jan 2025 18:28:34 +0800 Message-ID: <6f68ad68-c233-46b4-fb83-b09e21c8936f@huawei.com> Date: Sat, 4 Jan 2025 18:28:34 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH mpam/v6.10-rc1 RFC 0/4] arm_mpam: Fix several minor issues Content-Language: en-US To: James Morse CC: , , "Wangshaobo (bobo)" References: <20240722040140.515173-1-zengheng4@huawei.com> From: Zeng Heng In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemf100008.china.huawei.com (7.202.181.222) On 2024/12/21 1:51, James Morse wrote: > Hello! > > On 22/07/2024 05:01, Zeng Heng wrote: >> After completing the necessary software adaptation for the local chipset, >> the MPAM function is successfully enabled. After related tests are >> completed, some issues were discovered and here attempt to fix them. >> >> Hope to get some suggestions for modifications, if I miss any rules should >> be followed, please let me know. > > Sorry for the delay following these up - they should all be fixed in the newer > versions of the tree. I've added 'CC' tags to the patches you fixed here. > > > Thanks, > > James > Thanks for your reply! I have found they are all fixed in the latest branch already. For the MPAM driver, I have updated the Narrow-PARTID feature patchset. Please feel free to provide any comments or suggestions, if you were available. Here is the link to the v4 of the Narrow-PARTID feature: https://lore.kernel.org/all/20250104101224.873926-1-zengheng4@huawei.com/ Thank you in advance. Greetings for new year, Zeng Heng