devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Pierre Gondois <pierre.gondois@arm.com>, linux-kernel@vger.kernel.org
Cc: Sriranjani P <sriranjani.p@samsung.com>,
	Shashank Prashar <s.prashar@samsung.com>,
	Rob Herring <robh+dt@kernel.org>,
	Aswani Reddy <aswani.reddy@samsung.com>,
	devicetree@vger.kernel.org, Alim Akhtar <alim.akhtar@samsung.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob.Herring@arm.com
Subject: Re: (subset) [PATCH 20/20] arm64: dts: Update cache properties for tesla
Date: Mon, 7 Nov 2022 19:13:33 +0100	[thread overview]
Message-ID: <2d8b2d85-7bc6-026a-baf9-11a47171ddc5@linaro.org> (raw)
In-Reply-To: <166742051293.139492.11245653117636211417.b4-ty@linaro.org>

On 02/11/2022 21:21, Krzysztof Kozlowski wrote:
> On Mon, 31 Oct 2022 10:21:19 +0100, Pierre Gondois wrote:
>> The DeviceTree Specification v0.3 specifies that the cache node
>> 'compatible' and 'cache-level' properties are 'required'. Cf.
>> s3.8 Multi-level and Shared Cache Nodes
>>
>> The recently added init_of_cache_level() function checks
>> these properties. Add them if missing.
>>
>> [...]
> 
> Applied, thanks!
> 
> [20/20] arm64: dts: Update cache properties for tesla
>         https://git.kernel.org/krzk/linux/c/3f0d4a02c7490f1aa15764ed85dcf0881bf66b9e

Now dropped. I understand this is the intention/request of v2.

Best regards,
Krzysztof


  reply	other threads:[~2022-11-07 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221031092138epcas5p3070cc1775dafebe8d4abffcecaa860b0@epcas5p3.samsung.com>
2022-10-31  9:21 ` [PATCH 20/20] arm64: dts: Update cache properties for tesla Pierre Gondois
2022-11-02 20:21   ` (subset) " Krzysztof Kozlowski
2022-11-07 18:13     ` Krzysztof Kozlowski [this message]
2022-11-03  5:18   ` Alim Akhtar

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=2d8b2d85-7bc6-026a-baf9-11a47171ddc5@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Rob.Herring@arm.com \
    --cc=alim.akhtar@samsung.com \
    --cc=aswani.reddy@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.gondois@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=s.prashar@samsung.com \
    --cc=sriranjani.p@samsung.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).