mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: 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>, <nicolas.ferre@microchip.com>
Subject: Re: [PATCH] arm64: dts: microchip: add missing cache properties
Date: Wed, 17 May 2023 13:58:11 +0100	[thread overview]
Message-ID: <20230517-revivable-scuba-dc7ece33723c@wendy> (raw)
In-Reply-To: <67bf21d4cf9573233fc8154ae73b966adba6df09.camel@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]

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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-05-17 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 22:31 Krzysztof Kozlowski
2023-05-16 16:30 ` Krzysztof Kozlowski
2023-05-17 11:38   ` Steen Hegelund
2023-05-17 12:10     ` Krzysztof Kozlowski
2023-05-17 12:37       ` Conor Dooley
2023-05-17 12:46         ` Steen Hegelund
2023-05-17 12:58           ` Conor Dooley [this message]
2023-05-17 15:22             ` Nicolas Ferre
2023-05-17 12:23 ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230517-revivable-scuba-dc7ece33723c@wendy \
    --to=conor.dooley@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=daniel.machon@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh+dt@kernel.org \
    --cc=steen.hegelund@microchip.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®