[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2bfa6c0b-1f23-4d57-b618-688ed8dc7fae@kernel.org>
Date: Mon, 18 Aug 2025 08:32:29 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Kaustabh Chakraborty <kauschluss@...root.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/6] Support for Exynos7870's display stack (DECON,
MIPIPHY, DSIM, etc.)
On 17/08/2025 16:49, Kaustabh Chakraborty wrote:
> On 2025-08-13 07:58, Krzysztof Kozlowski wrote:
>> On 26/06/2025 22:13, Kaustabh Chakraborty wrote:
>>> This series implements changes in the SoC subsystem, which includes
>>> devicetree additions. It depends on all sub-series listed below:
>>> (Legend: [R]eviewed, [A]ccepted)
>>>
>>> exynosdrm-decon -
>>> https://lore.kernel.org/r/20250627-exynosdrm-decon-v3-0-5b456f88cfea@disroot.org
>>> exynos7870-mipi-phy A
>>> https://lore.kernel.org/r/20250612-exynos7870-mipi-phy-v1-0-3fff0b62d9d3@disroot.org
>>> exynos7870-mipi-phy-fix -
>>> https://lore.kernel.org/r/20250627-exynos7870-mipi-phy-fix-v1-0-2eefab8b50df@disroot.org
>>> exynos7870-dsim -
>>> https://lore.kernel.org/r/20250627-exynos7870-dsim-v2-0-1433b67378d3@disroot.org
>>> panel-samsung-s6e8aa5x01 -
>>> https://lore.kernel.org/r/20250625-panel-samsung-s6e8aa5x01-v3-0-9a1494fe6c50@disroot.org
>>> panel-synaptics-tddi -
>>> https://lore.kernel.org/r/20250625-panel-synaptics-tddi-v2-0-7a62ab1d13c7@disroot.org
>>>
>>> Signed-off-by: Kaustabh Chakraborty <kauschluss@...root.org>
>>
>> What is the status of the bindings from dependencies? I think they were
>> not accepted.
>
> Except panel-synaptics-tddi, all have been accepted. A lot of them
> haven't hit next though. I'm waiting for that to send the next revision.
What does it mean - accepted but not hit next? If it is accepted, it
must be visible in next. Which maintainer's tree are not in the next?
Best regards,
Krzysztof
Powered by blists - more mailing lists