[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <168683516438.2362648.11436943550545172181.b4-ty@ti.com>
Date: Thu, 15 Jun 2023 18:49:46 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>, Nishanth Menon <nm@...com>
CC: Vignesh Raghavendra <vigneshr@...com>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Tero Kristo <kristo@...nel.org>, Udit Kumar <u-kumar1@...com>,
Nitin Yadav <n-yadav@...com>,
Neha Malcom Francis <n-francis@...com>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH 0/6] arm64: dts: ti: k3-j7*: Add general purpose timers
Hi Nishanth Menon,
On Wed, 31 May 2023 16:32:09 -0500, Nishanth Menon wrote:
> Add pending general purpose timer support for various J7 family
>
> Full list of K3 SoCs:
> * AM625: already merged
> * AM62A7: https://lore.kernel.org/all/20230418012717.1230882-2-nm@ti.com/
> * AM64: https://lore.kernel.org/all/20230414073328.381336-2-nm@ti.com/
> * AM65: already merged
> * J7200: https://lore.kernel.org/all/20230426103219.1565266-1-u-kumar1@ti.com/ (needs a respin)
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/6] arm64: dts: ti: k3-j721e: Add general purpose timers
commit: 7f209dd1267ce2a4a5f6a9e4571858fa2d2e588c
[2/6] arm64: dts: ti: k3-j721e: Configure pinctrl for timer IO
commit: 72a44d1c473486582d1d6177404e2fa7adf531ac
[3/6] arm64: dts: ti: k3-j721s2: Add general purpose timers
commit: 835d04422f9d4c232c060150e696075cd34e081a
[4/6] arm64: dts: ti: k3-j721s2: Configure pinctrl for timer IO
commit: 1ecc75be7bc522941261b5eb0c315b09098a47f4
[5/6] arm64: dts: ti: k3-j784s4: Add general purpose timers
commit: 833377cf858b24d45e658454bcb683dd9076b576
[6/6] arm64: dts: ti: k3-j784s4: Configure pinctrl for timer IO
commit: 5a41bcff08f9c0705f4e6c576d168051a7b323be
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