Message-ID: <5c888a22-aa56-6d94-2d56-ac5c224f8565@ti.com>
Date:   Tue, 17 Jan 2023 19:11:10 +0530
From:   "Raghavendra, Vignesh" <vigneshr@...com>
To:     Pierre Gondois <pierre.gondois@....com>,
        <linux-kernel@...r.kernel.org>
CC:     Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@...adcom.com>,
        Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>,
        Tsahee Zidenberg <tsahee@...apurnalabs.com>,
        Antoine Tenart <atenart@...nel.org>,
        Brijesh Singh <brijeshkumar.singh@....com>,
        Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
        Tom Lendacky <thomas.lendacky@....com>,
        Neil Armstrong <neil.armstrong@...aro.org>,
        Kevin Hilman <khilman@...libre.com>,
        Jerome Brunet <jbrunet@...libre.com>,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
        Khuong Dinh <khuong@...amperecomputing.com>,
        Liviu Dudau <liviu.dudau@....com>,
        Sudeep Holla <sudeep.holla@....com>,
        Lorenzo Pieralisi <lpieralisi@...nel.org>,
        William Zhang <william.zhang@...adcom.com>,
        Anand Gore <anand.gore@...adcom.com>,
        Kursad Oney <kursad.oney@...adcom.com>,
        Rafał Miłecki <rafal@...ecki.pl>,
        Alim Akhtar <alim.akhtar@...sung.com>,
        Shawn Guo <shawnguo@...nel.org>, Li Yang <leoyang.li@....com>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        Chester Lin <clin@...e.com>,
        Andreas Färber <afaerber@...e.de>,
        Matthias Brugger <mbrugger@...e.com>,
        NXP S32 Linux Team <s32@....com>,
        Wei Xu <xuwei5@...ilicon.com>, Chanho Min <chanho.min@....com>,
        Andrew Lunn <andrew@...n.ch>,
        Gregory Clement <gregory.clement@...tlin.com>,
        Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
        Lars Povlsen <lars.povlsen@...rochip.com>,
        Steen Hegelund <Steen.Hegelund@...rochip.com>,
        Daniel Machon <daniel.machon@...rochip.com>,
        <UNGLinuxDriver@...rochip.com>,
        Avi Fishman <avifishman70@...il.com>,
        Tomer Maimon <tmaimon77@...il.com>,
        Tali Perry <tali.perry1@...il.com>,
        Patrick Venture <venture@...gle.com>,
        Nancy Yuen <yuenn@...gle.com>,
        Benjamin Fair <benjaminfair@...gle.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Magnus Damm <magnus.damm@...il.com>,
        Heiko Stuebner <heiko@...ech.de>,
        Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Jisheng Zhang <jszhang@...nel.org>, Nishanth Menon <nm@...com>,
        Tero Kristo <kristo@...nel.org>,
        Viorel Suman <viorel.suman@....com>,
        Abel Vesa <abelvesa@...nel.org>,
        Zhou Peng <eagle.zhou@....com>,
        Shenwei Wang <shenwei.wang@....com>,
        Peng Fan <peng.fan@....com>, Ming Qian <ming.qian@....com>,
        Tim Harvey <tharvey@...eworks.com>,
        Adam Ford <aford173@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>, Li Jun <jun.li@....com>,
        Richard Zhu <hongxing.zhu@....com>,
        Markus Niebel <Markus.Niebel@...tq-group.com>,
        Joakim Zhang <qiangqing.zhang@....com>,
        Marek Vasut <marex@...x.de>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Alexander Stein <alexander.stein@...tq-group.com>,
        Paul Elder <paul.elder@...asonboard.com>,
        Martin Kepplinger <martink@...teo.de>,
        David Heidelberg <david@...t.cz>,
        Oliver Graute <oliver.graute@...oconnector.com>,
        Liu Ying <victor.liu@....com>, Wei Fang <wei.fang@....com>,
        Clark Wang <xiaoning.wang@....com>,
        Jacky Bai <ping.bai@....com>,
        Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Vadym Kochan <vadym.kochan@...ision.eu>,
        Sameer Pujar <spujar@...dia.com>,
        Mikko Perttunen <mperttunen@...dia.com>,
        Prathamesh Shete <pshete@...dia.com>,
        Akhil R <akhilrajeev@...dia.com>,
        Sumit Gupta <sumitg@...dia.com>,
        Diogo Ivo <diogo.ivo@...nico.ulisboa.pt>,
        Vidya Sagar <vidyas@...dia.com>,
        Ashish Mhetre <amhetre@...dia.com>,
        Johan Jonker <jbx6244@...il.com>,
        Christopher Obbard <chris.obbard@...labora.com>,
        Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
        Aswani Reddy <aswani.reddy@...sung.com>,
        Shashank Prashar <s.prashar@...sung.com>,
        Arjun K V <arjun.kv@...sung.com>,
        <devicetree@...r.kernel.org>,
        <linux-rpi-kernel@...ts.infradead.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-amlogic@...ts.infradead.org>,
        <linux-samsung-soc@...r.kernel.org>,
        <linux-mediatek@...ts.infradead.org>, <openbmc@...ts.ozlabs.org>,
        <linux-tegra@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
        <linux-realtek-soc@...ts.infradead.org>,
        <linux-renesas-soc@...r.kernel.org>,
        <linux-rockchip@...ts.infradead.org>
Subject: Re: (subset) [PATCH v2 23/23] arm64: dts: Update cache properties for
 ti

Hi Pierre Gondois,

On 11/7/2022 9:27 PM, 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 'cache-unified' property should be present if one of the
> properties for unified cache is present ('cache-size', ...).
> 
> Update the Device Trees accordingly.

[...]

[23/23] arm64: dts: Update cache properties for ti
        commit: 880932e657ffc677c1b053a947afa87ffed1b29d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain
during the next merge window (or sooner if it is a relevant bug fix),
however if problems are discovered then the patch may be dropped or
reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh


[...]

Powered by blists - more mailing lists