From: Matthias Brugger <matthias.bgg@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mt8183-kukui: align SPI NOR node name with dtschema
Date: Wed, 20 Apr 2022 14:35:48 +0200 [thread overview]
Message-ID: <38f29c29-e3c2-240a-23a0-509c4febf1ca@gmail.com> (raw)
In-Reply-To: <165044570803.75184.17759035800452933385.b4-ty@linaro.org>
On 20/04/2022 11:10, Krzysztof Kozlowski wrote:
> On Thu, 7 Apr 2022 16:21:43 +0200, Krzysztof Kozlowski wrote:
>> The node names should be generic and SPI NOR dtschema expects "flash".
>>
>>
>
> Looks like no one wants to take this, so let me take care of it.
>
First thing would have been a ping on the patch, don't you think? Anyway as I
said the last time, if you take DTS patches for mediatek, I'd need a stable
branch I can merge so that we don't have any merge conflicts in the end.
Regards,
Matthias
> Applied, thanks!
>
> [1/1] arm64: dts: mt8183-kukui: align SPI NOR node name with dtschema
> commit: 4e3ffebd69e0aada1ce6bf4bf832e14a3c4f50db
>
> Best regards,
next prev parent reply other threads:[~2022-04-20 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:21 [PATCH] arm64: dts: mt8183-kukui: align SPI NOR node name with dtschema Krzysztof Kozlowski
2022-04-20 9:10 ` Krzysztof Kozlowski
2022-04-20 12:35 ` Matthias Brugger [this message]
2022-04-21 8:01 ` Krzysztof Kozlowski
2022-04-22 9:13 ` Matthias Brugger
2022-04-22 10:19 ` 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=38f29c29-e3c2-240a-23a0-509c4febf1ca@gmail.com \
--to=matthias.bgg@gmail.com \
--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=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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).