[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <85cfecd0-644d-4035-96bb-5b7752aecb04@kernel.org>
Date: Fri, 17 Jan 2025 10:23:28 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Shree Ramamoorthy <s-ramamoorthy@...com>, aaro.koskinen@....fi,
andreas@...nade.info, khilman@...libre.com, rogerq@...nel.org,
tony@...mide.com, lee@...nel.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: m-leonard@...com, praneeth@...com, christophe.jaillet@...adoo.fr
Subject: Re: [PATCH v1 0/1] Add TI TPS65214 PMIC MFD Support
On 16/01/2025 23:39, Shree Ramamoorthy wrote:
> TPS65214 is a Power Management Integrated Circuit (PMIC) that has
> significant register map overlap with TPS65215 and TPS65219. The series
> introduces TPS65214 and adds the device to the multi-PMIC support driver.
>
> This follow-up series is dependent on:
> Commit d23b7176df4a ("regulator: dt-bindings: Add TI TPS65214 PMIC bindings")
What is this commit? Which tree? Recent next does not have it.
The other thread said it depends on this patch, so how do you see it
being merged? A depends on B, B depends on A. If A gets merged first:
broken kernel. If B gets merged first: broken kernel? So what does this
dependency and commit even mean?
Best regards,
Krzysztof
Powered by blists - more mailing lists