[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6829146-1a5e-6132-1e8b-bcb39f8a904e@microchip.com>
Date: Wed, 6 Jul 2022 10:11:31 +0000
From: <Conor.Dooley@...rochip.com>
To: <sudeep.holla@....com>, <Conor.Dooley@...rochip.com>
CC: <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
<paul.walmsley@...ive.com>, <palmer@...belt.com>,
<aou@...s.berkeley.edu>, <Daire.McNamara@...rochip.com>,
<niklas.cassel@....com>, <damien.lemoal@...nsource.wdc.com>,
<geert@...ux-m68k.org>, <zong.li@...ive.com>, <kernel@...il.dk>,
<hahnjo@...njo.de>, <devicetree@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<Brice.Goglin@...ia.fr>
Subject: Re: [PATCH 0/5] RISC-V: Add cpu-map topology information nodes
On 06/07/2022 11:03, Sudeep Holla wrote:
> On Wed, Jul 06, 2022 at 09:43:02AM +0000, Conor.Dooley@...rochip.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 :)
Powered by blists - more mailing lists