From: Nishanth Menon <nm@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: Nishanth Menon <nm@ti.com>,
<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: (subset) [PATCH v4 0/3] arm64: dts: k3: Resolve remaining dtbs_check warnings
Date: Sat, 24 Aug 2024 14:54:48 -0500 [thread overview]
Message-ID: <172452924926.505816.7580905718644351705.b4-ty@ti.com> (raw)
In-Reply-To: <cover.1723653439.git.jan.kiszka@siemens.com>
Hi Jan Kiszka,
On Wed, 14 Aug 2024 18:37:16 +0200, Jan Kiszka wrote:
> Changes in v4:
> - drop no longer applicable mux-controller
> - model dss-oldi-io-ctrl@41e0 and clock-controller@4140 as regular property
>
> Changes in v3:
> - convert mux-controller from patternProperties to regular one
> - dropped k3-j72xx-mcu-wakeup patch after simple-bus conversion
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
I have picked Andrew's fixups, so just 1 patch in this series
is relevant. Let me know if you disagree. Thank you!
[1/3] arm64: dts: ti: k3-am642-evm: Silence schema warning
commit: 182a862560097dec7adf774af58076984cd6c1ed
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
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2024-08-24 19:54 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
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 ` Nishanth Menon [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=172452924926.505816.7580905718644351705.b4-ty@ti.com \
--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