Re: [PATCH 0/5] RISC-V: Add cpu-map topology information nodes

From: <Conor.Dooley@microchip.com>
To: <sudeep.holla@arm.com>, <Conor.Dooley@microchip.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
	<aou@eecs.berkeley.edu>, <Daire.McNamara@microchip.com>,
	<niklas.cassel@wdc.com>, <damien.lemoal@opensource.wdc.com>,
	<geert@linux-m68k.org>, <zong.li@sifive.com>, <kernel@esmil.dk>,
	<hahnjo@hahnjo.de>, <devicetree@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
	<Brice.Goglin@inria.fr>
Subject: Re: [PATCH 0/5] RISC-V: Add cpu-map topology information nodes
Date: Wed, 6 Jul 2022 10:11:31 +0000	[thread overview]
Message-ID: <c6829146-1a5e-6132-1e8b-bcb39f8a904e@microchip.com> (raw)
In-Reply-To: <20220706100333.7n35rfnbdrnz6mh5@bogus>

On 06/07/2022 11:03, Sudeep Holla wrote:
> On Wed, Jul 06, 2022 at 09:43:02AM +0000, Conor.Dooley@microchip.com wrote:
>> Cool, I'll respin a v2 without this included then & get the series
>> backported since this is user visible & will fix all existing supported
>> platforms.
>>
> 
> The DT /cpu-map is optional, so I don't think it needs to be backported.
> 
>>
>> I'll send the topology code changes separately to avoid it going
>> forwards.
> 
> This on the other hand can be backported to fix userspace.
> 

Uh sure, that sounds like a better idea (but more work lol).
No need for a v2 of this series then.

Thanks again :)