From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Bryan O'Donoghue <bod@kernel.org>, Robert Foss <rfoss@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dt-bindings: qcom,x1e80100-camss: Fix typo in CSIPHY supply description
Date: Wed, 17 Dec 2025 16:41:49 +0100 [thread overview]
Message-ID: <3f6f62f3-67be-4d3a-89ab-747e6acae29c@kernel.org> (raw)
In-Reply-To: <20251028111115.46261-2-krzysztof.kozlowski@linaro.org>
On 28/10/2025 12:11, Krzysztof Kozlowski wrote:
> Correct description of the CSIPHY 1.2 V supply
> ("vdd-csiphy-1p2-supply"), because it supplies 1.2 V, confirmed with DTS
> on the mailing lists.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../devicetree/bindings/media/qcom,x1e80100-camss.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Ping! It has been 1.5 months already. This also got other DT ack - TWO
DAYS after the posting - so why is this still not addressed by camss
maintainers?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-17 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 11:11 [PATCH] media: dt-bindings: qcom,x1e80100-camss: Fix typo in CSIPHY supply description Krzysztof Kozlowski
2025-10-30 16:50 ` Rob Herring (Arm)
2025-12-17 15:41 ` Krzysztof Kozlowski [this message]
2025-12-17 16:00 ` Krzysztof Kozlowski
2025-12-18 6:22 ` Bryan O'Donoghue
2025-12-18 6:44 ` Krzysztof Kozlowski
2025-12-18 6:47 ` Bryan O'Donoghue
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=3f6f62f3-67be-4d3a-89ab-747e6acae29c@kernel.org \
--to=krzk@kernel.org \
--cc=bod@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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