From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Raghavendra, Vignesh" <vigneshr@ti.com>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
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: ti: add missing cache properties
Date: Tue, 16 May 2023 19:26:09 +0200 [thread overview]
Message-ID: <2568ecb2-e97d-c61d-f68c-55a00b605bf6@linaro.org> (raw)
In-Reply-To: <e331d497-9b70-7895-24e1-8932457aa611@ti.com>
On 16/05/2023 19:04, Raghavendra, Vignesh wrote:
> Hi Krzysztof,
>
> On 5/16/2023 10:09 PM, Krzysztof Kozlowski wrote:
>>
>> On Sat, 22 Apr 2023 00:31:43 +0200, Krzysztof Kozlowski wrote:
>>> As all level 2 and level 3 caches are unified, add required
>>> cache-unified properties to fix warnings like:
>>>
>>> k3-am6528-iot2050-basic-pg2.dtb: l3-cache0: 'cache-unified' is a required property
>>>
>>>
>>
>> Applied, thanks!
>>
>> Please let me know if this should go through any other tree.
>>
>> [1/1] arm64: dts: ti: add missing cache properties
>> https://git.kernel.org/krzk/linux-dt/c/be9633397b9f268242724a0c763839579761ee60
>>
>> Best regards,
>
>
> I have already queued it up at [0] for testing (should be part of linux-next already)..
> I intend to send out this as part of fixes PR towards -rc3 tomo. Would you mind dropping this from your tree?
>
> [0] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git/commit/?h=ti-k3-dts-next&id=27244f81d6f6abbf06fc705a940ba650fd687b9f
Thanks for letting me know, I'll drop mine.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-05-16 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:31 [PATCH] arm64: dts: ti: add missing cache properties Krzysztof Kozlowski
2023-04-22 1:34 ` Nishanth Menon
2023-05-16 16:35 ` Krzysztof Kozlowski
2023-05-16 16:39 ` Krzysztof Kozlowski
2023-05-16 17:04 ` Raghavendra, Vignesh
2023-05-16 17:26 ` Krzysztof Kozlowski [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=2568ecb2-e97d-c61d-f68c-55a00b605bf6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).