Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <ef188e83-07e6-102a-9cb6-3966ab31fe79@microchip.com>
Date:   Wed, 17 May 2023 17:22:46 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Subject: Re: [PATCH] arm64: dts: microchip: add missing cache properties
Content-Language: en-US
To:     Conor Dooley <conor.dooley@microchip.com>,
        Steen Hegelund <steen.hegelund@microchip.com>
CC:     Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Lars Povlsen <lars.povlsen@microchip.com>,
        Daniel Machon <daniel.machon@microchip.com>,
        <UNGLinuxDriver@microchip.com>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        <linux-kernel@vger.kernel.org>
References: <20230421223155.115339-1-krzysztof.kozlowski@linaro.org>
 <151169f7-dcdb-47f1-9616-67c3c388a233@linaro.org>
 <7772a5981d9a3d46056a53997162d1d75d22a701.camel@microchip.com>
 <41c72642-7d46-d7d1-d49a-6bef685f934c@linaro.org>
 <20230517-crop-limeade-73369ac8594d@wendy>
 <67bf21d4cf9573233fc8154ae73b966adba6df09.camel@microchip.com>
 <20230517-revivable-scuba-dc7ece33723c@wendy>
From:   Nicolas Ferre <nicolas.ferre@microchip.com>
Organization: microchip
In-Reply-To: <20230517-revivable-scuba-dc7ece33723c@wendy>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 17/05/2023 at 14:58, Conor Dooley wrote:
> On Wed, May 17, 2023 at 02:46:38PM +0200, Steen Hegelund wrote:
>> On Wed, 2023-05-17 at 13:37 +0100, Conor Dooley wrote:
>>> On Wed, May 17, 2023 at 02:10:53PM +0200, Krzysztof Kozlowski wrote:
> 
>>>> For future (and all previous patches), please think what do you
>>>> (you=Microchip) want to do with it. If you do not handle the patches,
>>>> then someone should or the platform should be marked as "Odd fixes".
>>>
>>> If noone is set up to actually be the maintainer of the tree, and the
>>> patch volume is low, it might be a good idea to combine its maintenance
>>> with some of the other microchip trees.
>>>
>>> I've added Nicolas to CC here, since he is the main maintainer for the
>>> 32-bit ARM Microchip stuff. For some context, I maintain the RISC-V
>>> Microchip bits and a few other things like dt-bindings and some
>>> non-microchip RISC-V platforms.
>>>
>>> If you like, I could easily pick up patches for
>>> arch/arm64/boot/dts/microchip/* as I am already sending PRs to Arnd for
>>> other trees and another branch would not be much overhead!
>>>
>>> Clearly I do not know the hardware at all, and reviewing the patches
>>> would still be up to you, but I could handle the "administrative" side
>>> of things (applying the patches & sending PRs) if that would be helpful?
>>>
>>> Otherwise, Nicolas & I could probably help you through setting things up
>>> to send PRs without taking up Krzysztof's time?
>>>
>>> Either works for me!
>>
>> It would be preferable for me if you (Conor) would handle the
>> arch/arm64/boot/dts/microchip/* tree as you suggested.  It is not often we
>> update it, so it will hopefully be low overhead for you.
> 
> Okay. I will send a patch for MAINTAINERS then - although I'll give
> Nicolas a change to look at it this thread first ;)

Yes, sure thing that I can be added as maintainer of the arm64 part of 
Microchip, you can add me to a MAINTAINERS entry taking care of this and 
use our group git tree for this purpose, we'll add branches for that.

> If the mpu32 guys ever decide to become mpu64 then we can perhaps
> re-visit things.
> 
>> Thanks to both of you for the assistance.
 >
> No worries chief.

Thanks Conor for the heads-up. Best regards,
   Nicolas

-- 
Nicolas Ferre