linux-kernel - Re: [PATCH v3 -next] drm/display: Fix build error without CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACRpkda6OY3Cp0+pWmg0E=9nRLbEmwp8x0rF81McYFHVnTno1A@mail.gmail.com>
Date:   Thu, 23 Jun 2022 16:18:45 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     YueHaibing <yuehaibing@...wei.com>
Cc:     airlied@...ux.ie, daniel@...ll.ch, tzimmermann@...e.de,
        lyude@...hat.com, dri-devel@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org, dmitry.baryshkov@...aro.org,
        quic_abhinavk@...cinc.com
Subject: Re: [PATCH v3 -next] drm/display: Fix build error without CONFIG_OF

On Sat, Jun 11, 2022 at 6:16 AM YueHaibing <yuehaibing@...wei.com> wrote:

> While CONFIG_OF is n but COMPILE_TEST is y, we got this:
>
> WARNING: unmet direct dependencies detected for DRM_DP_AUX_BUS
>   Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && OF [=n]
>   Selected by [y]:
>   - DRM_MSM [=y] && HAS_IOMEM [=y] && DRM [=y] && (ARCH_QCOM || SOC_IMX5 || COMPILE_TEST [=y]) && COMMON_CLK [=y] && IOMMU_SUPPORT [=y] && (QCOM_OCMEM [=n] || QCOM_OCMEM [=n]=n) && (QCOM_LLCC [=y] || QCOM_LLCC [=y]=n) && (QCOM_COMMAND_DB [=n] || QCOM_COMMAND_DB [=n]=n)
>
> Make DRM_DP_AUX_BUS depends on OF || COMPILE_TEST to fix this warning.
>
> Fixes: 1e0f66420b13 ("drm/display: Introduce a DRM display-helper module")
> Signed-off-by: YueHaibing <yuehaibing@...wei.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> Reviewed-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
> Acked-by: Linus Walleij <linus.walleij@...aro.org>
> ---
> v3: use correct Fixes tag

Patch applied for next as non-urgent fix.

Yours,
Linus Walleij