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 ;) 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.
Attachment:
signature.asc
Description: PGP signature
