From: Nishanth Menon <nm@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Bao Cheng Su <baocheng.su@siemens.com>,
Diogo Ivo <diogo.ivo@siemens.com>
Subject: Re: [PATCH v4 2/3] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain
Date: Tue, 27 Aug 2024 06:38:22 -0500 [thread overview]
Message-ID: <20240827113822.y3gyvo6ndwxpzg7z@entrust> (raw)
In-Reply-To: <8de13103-cd57-407c-839c-843dcedbac29@siemens.com>
On 22:13-20240826, Jan Kiszka wrote:
[..]
> I don't mind via which patches we finally get to zero dtbs_check
> warnings, just that we get there.
Sure. Since we are on the cleanup path towards simple-bus, lets just get
there.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-08-27 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 16:37 [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings Jan Kiszka
2024-08-14 16:37 ` [PATCH v4 1/3] arm64: dts: ti: k3-am642-evm: Silence schema warning Jan Kiszka
2024-08-14 16:37 ` [PATCH v4 2/3] dt-bindings: soc: ti: am645-system-controller: add child nodes used by main domain Jan Kiszka
2024-08-15 15:24 ` Conor Dooley
2024-08-24 17:58 ` Nishanth Menon
2024-08-26 11:31 ` Jan Kiszka
2024-08-26 11:42 ` Nishanth Menon
2024-08-26 12:01 ` Jan Kiszka
2024-08-26 19:59 ` Nishanth Menon
2024-08-26 20:13 ` Jan Kiszka
2024-08-27 11:38 ` Nishanth Menon [this message]
2024-08-14 16:37 ` [PATCH v4 3/3] arm64: dts: ti: k3-am65-main: add system controller compatible Jan Kiszka
2024-08-24 19:54 ` (subset) [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings Nishanth Menon
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=20240827113822.y3gyvo6ndwxpzg7z@entrust \
--to=nm@ti.com \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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