All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mohit Dsor" <mohit.dsor@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: defconfig: Enable LT9611C bridge driver
Date: Wed, 07 Oct 2026 12:55:37 +0000	[thread overview]
Message-ID: <sashiko-outbox-163013@kernel.org> (raw)
In-Reply-To: <20261007-master_lt9611uxd-v4-2-9986704e2a7b@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: undefined CONFIG_DRM_LONTIUM_LT9611C added to defconfig
--

commit d7fcead75041287b78534a901e1cd8e93f2636d2
Author: Mohit Dsor <mohit.dsor@oss.qualcomm.com>

arm64: defconfig: Enable LT9611C bridge driver
    
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.

> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index fce418fe6ff65..b4be8ec8d4c86 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -977,6 +977,7 @@ CONFIG_DRM_I2C_NXP_TDA998X=m
>  CONFIG_DRM_ITE_IT6263=m
>  CONFIG_DRM_LONTIUM_LT8912B=m
>  CONFIG_DRM_LONTIUM_LT9611=m
> +CONFIG_DRM_LONTIUM_LT9611C=m

[Severity: Low]
Is this the intended Kconfig symbol?

The symbol CONFIG_DRM_LONTIUM_LT9611C is undefined in the Kconfig system.
Adding an undefined symbol to defconfig acts as a no-op, and the build system
will silently drop it during the build process.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261007-master_lt9611uxd-v4-0-9986704e2a7b@oss.qualcomm.com?part=2

  reply	other threads:[~2026-10-07 12:55 UTC|newest]

Thread overview: 10+ 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-12 18:55     ` Mohit Dsor
2026-10-07 12:51 ` [PATCH v4 2/2] arm64: defconfig: Enable LT9611C bridge driver Mohit Dsor
2026-10-07 12:55   ` sashiko-bot [this message]
2026-10-07 13:41   ` Dmitry Baryshkov
2026-10-09 11:50   ` Krzysztof Kozlowski
2026-10-12 18:56     ` Mohit Dsor

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=sashiko-outbox-163013@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=mohit.dsor@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.