[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xq67rd3a6yeie3kajdnzufbxctqxmv2h3ufhqauoqmxe3hk2oa@vnru4lmtpkm3>
Date: Fri, 27 Dec 2024 08:42:21 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Uwe Kleine-König <ukleinek@...nel.org>
Cc: Kever Yang <kever.yang@...k-chips.com>, heiko@...ech.de,
linux-rockchip@...ts.infradead.org, linux-pwm@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>,
Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzk+dt@...nel.org>, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 11/17] dt-bindings: pwm: rockchip: Add
rockchip,rk3562-pwm
On Fri, Dec 27, 2024 at 08:24:15AM +0100, Uwe Kleine-König wrote:
> On Tue, Dec 24, 2024 at 05:49:14PM +0800, Kever Yang wrote:
> > Add rockchip,rk3562-pwm compatible string.
> >
> > Signed-off-by: Kever Yang <kever.yang@...k-chips.com>
>
> What is your merge plan here? From my POV merging the pwm update via my
> pwm tree would be the easiest. But if you want to let it go via (say)
No clue, but we already provided feedback this is supposed to be split
per subsystem. Not much improved.
Best regards,
Krzysztof
Powered by blists - more mailing lists