From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) (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 32C104CB23 for ; Tue, 2 Jul 2024 07:45:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.188 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719906303; cv=none; b=FJF23Xv/qzzrFNJOJI0/7MIswGPugptbG2KmVjkvfkVFPYWqkXOO2UFec0Ypc5yKPIhA2t496zFQYacbScC+rJZkVGvzgZfpXQqxZTWFY+8F3xiemEPolcIWjBSAhLh/j8uChnmkVIJjcCktK49YmxHP0KTf/nnxlvm0bs+WDys= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719906303; c=relaxed/simple; bh=zBp+Mi0WuvTANNUQHSNKoWAMetKEODtoHLldptsiNIA=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=UP9NCv/Q6SzZ6JQKpUJZD+m22N0F4fRxq1nVUQFNTJb4F/h5xGOMXP63b9JxMThexKfLuZwc8ABhKqDxghFbBB4r8bYSgPwwJP4jatv8AXgTAKnhLO+Cy1tEw2EVkttai2BKv9Tp0mhF5jTulZ2nt2ZQcXboQO8j933JYybpKQM= 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.188 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.88.105]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4WCvzF6k6Hzdfx9; Tue, 2 Jul 2024 15:43:21 +0800 (CST) Received: from kwepemi100008.china.huawei.com (unknown [7.221.188.57]) by mail.maildlp.com (Postfix) with ESMTPS id 8BE94140488; Tue, 2 Jul 2024 15:44:58 +0800 (CST) Received: from [10.67.109.254] (10.67.109.254) by kwepemi100008.china.huawei.com (7.221.188.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Tue, 2 Jul 2024 15:44:57 +0800 Message-ID: Date: Tue, 2 Jul 2024 15:44:56 +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.2.0 Subject: Re: [PATCH 0/2] ARM: 9322/1: Switch over to GENERIC_CPU_DEVICES Content-Language: en-US To: "Russell King (Oracle)" CC: , , , , , , , , , , , , References: <20240702065906.929987-1-ruanjinjie@huawei.com> From: Jinjie Ruan In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: dggems702-chm.china.huawei.com (10.3.19.179) To kwepemi100008.china.huawei.com (7.221.188.57) On 2024/7/2 15:30, Russell King (Oracle) wrote: > What's going on with the subject in all of this series? Why does it > contain: > > "ARM: 9322/1" > > ? > > We already have: > "3562257b3416 ARM: 9322/1: Explicitly include correct DT includes" > > Merged in the kernel tree, and this has nothing to do with it. Moreover, > these numbers are generated by the patch system and are supposed to be > unique to each patch. The title refers to "git log --online arch/arm/kernel/setup.c", I misunderstood its meaning, I'll resend it and remove it, thank you very much. > > On Tue, Jul 02, 2024 at 02:59:04PM +0800, Jinjie Ruan wrote: >> Currently, almost all architectures have switched to GENERIC_CPU_DEVICES, >> except for arm32. Also switch over to GENERIC_CPU_DEVICES, which can also >> make the code more concise. >> >> Jinjie Ruan (2): >> ARM: 9322/1: Switch over to GENERIC_CPU_DEVICES using >> arch_register_cpu() >> ARM: 9322/1: Convert to arch_cpu_is_hotpluggable() >> >> arch/arm/Kconfig | 1 + >> arch/arm/include/asm/cpu.h | 1 - >> arch/arm/kernel/setup.c | 14 ++------------ >> 3 files changed, 3 insertions(+), 13 deletions(-) >> >> -- >> 2.34.1 >> >> >