From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mohit Dsor <mohit.dsor@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, venkata.valluru@oss.qualcomm.com,
Jessica Zhang <jesszhan0024@gmail.com>
Subject: Re: [PATCH v4 2/2] arm64: defconfig: Enable LT9611C bridge driver
Date: Fri, 9 Oct 2026 13:50:39 +0200 [thread overview]
Message-ID: <701e5e45-f607-452d-8223-c987427fb34f@kernel.org> (raw)
In-Reply-To: <20261007-master_lt9611uxd-v4-2-9986704e2a7b@oss.qualcomm.com>
On 07/10/2026 14:51, Mohit Dsor wrote:
> Enable the Lontium LT9611C DSI-to-HDMI bridge driver as a module.
> This driver supports the LT9611UXD chip used on the Shikra IQS EVK
> board to provide HDMI output via the MDSS DSI interface.
Same feedback as v1. Why every second defconfig patch from Qualcomm
completely ignores the fact that this is not a Qualcomm-only or
Qualcomm-specific defconfig?
Best regards,
Krzysztof
prev parent reply other threads:[~2026-10-09 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 12:51 [PATCH v4 0/2] arm64: qcom: shikra-iqs-evk: Add LT9611UXD HDMI bridge support Mohit Dsor
2026-10-07 12:51 ` [PATCH v4 1/2] arm64: dts: " Mohit Dsor
2026-10-07 12:59 ` sashiko-bot
2026-10-07 13:40 ` Dmitry Baryshkov
2026-10-07 12:51 ` [PATCH v4 2/2] arm64: defconfig: Enable LT9611C bridge driver Mohit Dsor
2026-10-07 12:55 ` sashiko-bot
2026-10-07 13:41 ` Dmitry Baryshkov
2026-10-09 11:50 ` Krzysztof Kozlowski [this message]
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=701e5e45-f607-452d-8223-c987427fb34f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jesszhan0024@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohit.dsor@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=venkata.valluru@oss.qualcomm.com \
/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