From: Dragan Simic <dsimic@manjaro.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org,
Anand Moon <linux.amoon@gmail.com>,
conor+dt@kernel.org, didi.debian@cknow.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Add cache information to the SoC dtsi for RK3328
Date: Mon, 25 Mar 2024 03:41:37 +0100 [thread overview]
Message-ID: <e3eebf444a5440a983f5848c0d7af1e3@manjaro.org> (raw)
In-Reply-To: <171131986742.918919.14220098959078401116.b4-ty@sntech.de>
On 2024-03-24 23:38, Heiko Stuebner wrote:
> On Sat, 9 Mar 2024 05:24:42 +0100, Dragan Simic wrote:
>> Add missing cache information to the Rockchip RK3328 SoC dtsi, to
>> allow
>> the userspace, which includes lscpu(1) that uses the virtual files
>> provided
>> by the kernel under the /sys/devices/system/cpu directory, to display
>> the
>> proper RK3328 cache information.
>>
>> While there, use a more self-descriptive label for the L2 cache node,
>> which
>> also makes it more consistent with other SoC dtsi files.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] arm64: dts: rockchip: Add cache information to the SoC dtsi for
> RK3328
> commit: 67a6a98575974416834c2294853b3814376a7ce7
Great, thanks!
_______________________________________________
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:[~2024-03-25 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 4:24 [PATCH v2] arm64: dts: rockchip: Add cache information to the SoC dtsi for RK3328 Dragan Simic
2024-03-24 22:38 ` Heiko Stuebner
2024-03-25 2:41 ` Dragan Simic [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=e3eebf444a5440a983f5848c0d7af1e3@manjaro.org \
--to=dsimic@manjaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--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