From: Nishanth Menon <nm@ti.com>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Ivan Khoronzhuk" <ivan.khoronzhuk@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Nishanth Menon <nm@ti.com>, <mfd@lists.linux.dev>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<goledhruva@gmail.com>, <m-chawdhry@ti.com>,
<daniel.baluta@gmail.com>, <simona.toaca@nxp.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: (subset) [PATCH v4 0/2] ti,keystone-devctrl: Convert to DT schema and DTS cleanups
Date: Fri, 4 Sep 2026 10:59:38 -0500 [thread overview]
Message-ID: <178853756367.2995941.13597621016722983915.b4-ty@b4> (raw)
In-Reply-To: <20260901-ti-keystone-devctrl-v4-0-2922f2a44792@gmail.com>
Hi Bhargav Joshi,
On Tue, 01 Sep 2026 05:08:11 +0530, Bhargav Joshi wrote:
> Series converts Texas Instruments Keystone Device State Control binding
> to DT schema and aligns the existing dt files with standard naming
> conventions.
>
> Patch 1 aligns the legacy child node names with standard names.
> Patch 2 converts the ti,keystone-devctrl binding to YAML schema.
>
> [...]
Please note: Bindings need to go through appropriate maintainers.
I have applied the following to branch ti-keystone-dts-next on [1].
Thank you!
[1/2] ARM: dts: ti: keystone: Align devctrl child node names with dtschema
commit: 386cccc12a856a376da20ac9e93827ecd49352e7
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
https://ti.com/opensource
prev parent reply other threads:[~2026-09-04 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:38 [PATCH v4 0/2] ti,keystone-devctrl: Convert to DT schema and DTS cleanups Bhargav Joshi
2026-08-31 23:38 ` [PATCH v4 1/2] ARM: dts: ti: keystone: Align devctrl child node names with dtschema Bhargav Joshi
2026-08-31 23:49 ` sashiko-bot
2026-08-31 23:38 ` [PATCH v4 2/2] dt-bindings: mfd: ti,keystone-devctrl: Convert to DT schema Bhargav Joshi
2026-08-31 23:50 ` sashiko-bot
2026-09-04 15:59 ` 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=178853756367.2995941.13597621016722983915.b4-ty@b4 \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=goledhruva@gmail.com \
--cc=ivan.khoronzhuk@ti.com \
--cc=j.bhargav.u@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=simona.toaca@nxp.com \
--cc=ssantosh@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