From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7286C072B5 for ; Fri, 24 May 2019 09:38:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A541620645 for ; Fri, 24 May 2019 09:38:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390185AbfEXJiw (ORCPT ); Fri, 24 May 2019 05:38:52 -0400 Received: from foss.arm.com ([217.140.101.70]:38156 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389881AbfEXJiw (ORCPT ); Fri, 24 May 2019 05:38:52 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C6D65A78; Fri, 24 May 2019 02:38:51 -0700 (PDT) Received: from fuggles.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 1FD4E3F703; Fri, 24 May 2019 02:38:47 -0700 (PDT) Date: Fri, 24 May 2019 10:38:41 +0100 From: Will Deacon To: Sudeep Holla Cc: Greg Kroah-Hartman , Atish Patra , linux-kernel@vger.kernel.org, Jeffrey Hugo , Albert Ou , Andreas Schwab , Anup Patel , Catalin Marinas , devicetree@vger.kernel.org, Ingo Molnar , Jeremy Linton , linux-riscv@lists.infradead.org, Mark Rutland , Morten Rasmussen , Otto Sabart , Palmer Dabbelt , Paul Walmsley , "Peter Zijlstra (Intel)" , "Rafael J. Wysocki" , Rob Herring , Thomas Gleixner , linux-arm-kernel@lists.infradead.org Subject: Re: [RFT PATCH v5 3/5] cpu-topology: Move cpu topology code to common code. Message-ID: <20190524093754.GA3432@fuggles.cambridge.arm.com> References: <20190524000653.13005-1-atish.patra@wdc.com> <20190524000653.13005-4-atish.patra@wdc.com> <20190524081333.GA15566@kroah.com> <20190524085720.GA13121@e107155-lin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190524085720.GA13121@e107155-lin> User-Agent: Mutt/1.11.1+86 (6f28e57d73f2) () Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 09:57:40AM +0100, Sudeep Holla wrote: > On Fri, May 24, 2019 at 10:13:33AM +0200, Greg Kroah-Hartman wrote: > > On Thu, May 23, 2019 at 05:06:50PM -0700, Atish Patra wrote: > > > Both RISC-V & ARM64 are using cpu-map device tree to describe > > > their cpu topology. It's better to move the relevant code to > > > a common place instead of duplicate code. > > > > > > Signed-off-by: Atish Patra > > > Tested-by: Jeffrey Hugo > > > --- > > > arch/arm64/include/asm/topology.h | 23 --- > > > arch/arm64/kernel/topology.c | 303 +----------------------------- > > > drivers/base/arch_topology.c | 296 +++++++++++++++++++++++++++++ > > > include/linux/arch_topology.h | 28 +++ > > > include/linux/topology.h | 1 + > > > 5 files changed, 329 insertions(+), 322 deletions(-) > > > > What, now _I_ have to maintain drivers/base/arch_topology.c? That's > > nice for everyone else, but not me :( > > > > Ugh. > > > > Anyway, what are you wanting to happen to this series? I think we need > > some ARM people to sign off on it before I can take the whole thing, > > right? > > > > Greg, I am ready to take ownership. Juri the original author of this file > agreed and I have been reviewing this file since Juri first wrote it. > I am happy to submit a patch assuming maintainership for this file, was > just waiting to hear from you when I asked explicitly you and Juri in > last version of the patch when Will wanted someone from ARM to be reviewer > of this file at-least. I am happy to take over as reviewer or maintainer > which ever you prefer. Yes, please just include this update to MAINTAINERS as part of the series. I'll ack it. Will