[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2364081.ElGaqSPkdT@diego>
Date: Tue, 18 Mar 2025 10:15:21 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, detlev.casanova@...labora.com,
sebastian.reichel@...labora.com
Subject: Re: (subset) [PATCH RESEND v2 0/6] RK3576 OTP support
Hi,
Am Montag, 17. Februar 2025, 10:53:16 MEZ schrieb Srinivas Kandagatla:
>
> On Mon, 10 Feb 2025 23:45:04 +0100, Heiko Stuebner wrote:
> > This enables OTP support in the nvmem driver for rk3576.
> >
> > I expect to pick the clock patch (patch1) and the arm64-dts patch (patch6)
> > myself, after the nvmem-driver and -binding patches have been applied
> > (patches 2-5).
> >
> > But kept them together for people wanting to try this series.
> >
> > [...]
>
> Applied, thanks!
>
> [1/6] clk: rockchip: rk3576: define clk_otp_phy_g
> commit: 3e081aa132bbefe31ac95dd6dfc8d787ffa83d0b
the applied message says you picked the clock patch, but it's not in your
tree - probably because you realized that it's a clock patch? :-)
So just to make sure it doesn't land in two trees, I should probably pick
up the patch for the Rockchip clock driver, right?
Thanks a lot
Heiko
> [2/6] nvmem: rockchip-otp: Move read-offset into variant-data
> commit: 024e21343f3cbcde0343473fcaf094d2c19cc7bf
> [3/6] dt-bindings: nvmem: rockchip,otp: add missing limits for clock-names
> commit: a1bf00100d06ad69286154a63e548ae6f6ce8539
> [4/6] dt-bindings: nvmem: rockchip,otp: Add compatible for RK3576
> commit: 8c94337ebbfb840944574f82df0cbe35930d8df8
> [5/6] nvmem: rockchip-otp: add rk3576 variant data
> commit: c5ebefe4e20d9fd99ae49cbfd1c18632cf338fa5
>
> Best regards,
>
Powered by blists - more mailing lists