All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh@kernel.org>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-ap810: Fix GICv3 ITS node name
Date: Tue, 14 Mar 2023 17:41:34 +0100	[thread overview]
Message-ID: <ed2d01ee-4e64-396b-569e-e698ea6fd5da@linaro.org> (raw)
In-Reply-To: <c02f83c4-3796-40ad-8087-d297ba84e5da@lunn.ch>

On 14/03/2023 17:21, Andrew Lunn wrote:
> On Tue, Mar 14, 2023 at 10:22:40AM -0500, Rob Herring wrote:
>> On Tue, Feb 7, 2023 at 5:47 PM Rob Herring <robh@kernel.org> wrote:
>>>
>>> The GICv3 ITS is an MSI controller, therefore its node name should be
>>> 'msi-controller'.
>>>
>>> Signed-off-by: Rob Herring <robh@kernel.org>
>>> ---
>>>  arch/arm64/boot/dts/marvell/armada-ap810-ap0.dtsi | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Ping!
>>
>> If not maintained, should I send a patch removing this platform instead?
> 
> Gregory usually picks these up around -rc6.

Hm, so they stay in next for just one or two weeks before sending to
arm-soc? Why? They should be in the next as fast as possible, why waiting?

Second question, shall I drop it?

Best regards,
Krzysztof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>, Rob Herring <robh@kernel.org>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-ap810: Fix GICv3 ITS node name
Date: Tue, 14 Mar 2023 17:41:34 +0100	[thread overview]
Message-ID: <ed2d01ee-4e64-396b-569e-e698ea6fd5da@linaro.org> (raw)
In-Reply-To: <c02f83c4-3796-40ad-8087-d297ba84e5da@lunn.ch>

On 14/03/2023 17:21, Andrew Lunn wrote:
> On Tue, Mar 14, 2023 at 10:22:40AM -0500, Rob Herring wrote:
>> On Tue, Feb 7, 2023 at 5:47 PM Rob Herring <robh@kernel.org> wrote:
>>>
>>> The GICv3 ITS is an MSI controller, therefore its node name should be
>>> 'msi-controller'.
>>>
>>> Signed-off-by: Rob Herring <robh@kernel.org>
>>> ---
>>>  arch/arm64/boot/dts/marvell/armada-ap810-ap0.dtsi | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Ping!
>>
>> If not maintained, should I send a patch removing this platform instead?
> 
> Gregory usually picks these up around -rc6.

Hm, so they stay in next for just one or two weeks before sending to
arm-soc? Why? They should be in the next as fast as possible, why waiting?

Second question, shall I drop it?

Best regards,
Krzysztof


  reply	other threads:[~2023-03-14 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 23:47 [PATCH] arm64: dts: marvell: armada-ap810: Fix GICv3 ITS node name Rob Herring
2023-02-07 23:47 ` Rob Herring
2023-03-14 15:22 ` Rob Herring
2023-03-14 15:22   ` Rob Herring
2023-03-14 15:34   ` Krzysztof Kozlowski
2023-03-14 15:34     ` Krzysztof Kozlowski
2023-03-14 16:21   ` Andrew Lunn
2023-03-14 16:21     ` Andrew Lunn
2023-03-14 16:41     ` Krzysztof Kozlowski [this message]
2023-03-14 16:41       ` Krzysztof Kozlowski
2023-03-14 18:23     ` Rob Herring
2023-03-14 18:23       ` Rob Herring
2023-03-14 15:35 ` Krzysztof Kozlowski
2023-03-14 15:35   ` Krzysztof Kozlowski
2023-04-07 15:11   ` Gregory CLEMENT
2023-04-07 15:11     ` Gregory CLEMENT

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=ed2d01ee-4e64-396b-569e-e698ea6fd5da@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.