From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: marvell: armada-ap810: Fix GICv3 ITS node name
Date: Fri, 07 Apr 2023 17:11:14 +0200 [thread overview]
Message-ID: <87v8i73ey5.fsf@BL-laptop> (raw)
In-Reply-To: <167880811569.329316.7671442810659168728.b4-ty@linaro.org>
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:
> On Tue, 7 Feb 2023 17:47:35 -0600, Rob Herring wrote:
>> The GICv3 ITS is an MSI controller, therefore its node name should be
>> 'msi-controller'.
>>
>>
>
> Applied, thanks! Let me know if anyone else wants to take it instead.
>
> [1/1] arm64: dts: marvell: armada-ap810: Fix GICv3 ITS node name
> https://git.kernel.org/krzk/linux-dt/c/fce7defb8a46c31cf9384fee6e4b1e4920c46ff7
Let's hope it won't cause merge issue.
Gregory
>
> Best regards,
> --
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-04-07 15:12 UTC|newest]
Thread overview: 8+ 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-03-14 15:22 ` Rob Herring
2023-03-14 15:34 ` Krzysztof Kozlowski
2023-03-14 16:21 ` Andrew Lunn
2023-03-14 16:41 ` Krzysztof Kozlowski
2023-03-14 18:23 ` Rob Herring
2023-03-14 15:35 ` Krzysztof Kozlowski
2023-04-07 15:11 ` Gregory CLEMENT [this message]
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=87v8i73ey5.fsf@BL-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).