linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Support for Exynos7870's display stack (DECON, MIPIPHY, DSIM, etc.)
Date: Mon, 18 Aug 2025 08:32:29 +0200	[thread overview]
Message-ID: <2bfa6c0b-1f23-4d57-b618-688ed8dc7fae@kernel.org> (raw)
In-Reply-To: <45fc52d9988d1bf17eca392364c63193@disroot.org>

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@disroot.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


  reply	other threads:[~2025-08-18  6:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 20:13 [PATCH v2 0/6] Support for Exynos7870's display stack (DECON, MIPIPHY, DSIM, etc.) Kaustabh Chakraborty
2025-06-26 20:13 ` [PATCH v2 1/6] dt-bindings: samsung: exynos-sysreg: add exynos7870 sysregs Kaustabh Chakraborty
2025-06-27 21:41   ` Rob Herring (Arm)
2025-06-26 20:13 ` [PATCH v2 2/6] dt-bindings: soc: samsung: exynos-pmu: allow mipi-phy subnode Kaustabh Chakraborty
2025-06-27 21:42   ` Rob Herring
2025-06-28  7:19     ` Kaustabh Chakraborty
2025-06-28  9:33       ` Krzysztof Kozlowski
2025-06-26 20:13 ` [PATCH v2 3/6] arm64: dts: exynos7870: add DSI support Kaustabh Chakraborty
2025-08-13  7:56   ` Krzysztof Kozlowski
2025-08-17 14:40     ` Kaustabh Chakraborty
2025-06-26 20:13 ` [PATCH v2 4/6] arm64: dts: exynos7870-on7xelte: enable display panel support Kaustabh Chakraborty
2025-06-26 20:13 ` [PATCH v2 5/6] arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty
2025-06-26 20:13 ` [PATCH v2 6/6] arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-06-27 14:06 ` [PATCH v2 0/6] Support for Exynos7870's display stack (DECON, MIPIPHY, DSIM, etc.) Rob Herring (Arm)
2025-08-13  7:58 ` Krzysztof Kozlowski
2025-08-17 14:49   ` Kaustabh Chakraborty
2025-08-18  6:32     ` Krzysztof Kozlowski [this message]
2025-08-18 17:08       ` Kaustabh Chakraborty
2025-08-24 10:25         ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2bfa6c0b-1f23-4d57-b618-688ed8dc7fae@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kauschluss@disroot.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).