From: YueHaibing <yuehaibing@huawei.com>
To: <xinliang.liu@linaro.org>, <tiantao6@hisilicon.com>,
<jstultz@google.com>, <kong.kongxinwei@hisilicon.com>,
<puck.chen@hisilicon.com>, <airlied@linux.ie>, <daniel@ffwll.ch>,
<tzimmermann@suse.de>, <javierm@redhat.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] drm/hisilicon/hibmc: Fix COMPILE_TEST building without MMU
Date: Wed, 14 Sep 2022 14:44:03 +0800 [thread overview]
Message-ID: <584a67fa-cc1d-a30b-ccac-847f717b6d90@huawei.com> (raw)
In-Reply-To: <20220823020920.11008-1-yuehaibing@huawei.com>
ping...
On 2022/8/23 10:09, YueHaibing wrote:
> WARNING: unmet direct dependencies detected for DRM_TTM
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
> Selected by [y]:
> - DRM_TTM_HELPER [=y] && HAS_IOMEM [=y] && DRM [=y]
> - DRM_HISI_HIBMC [=y] && HAS_IOMEM [=y] && DRM [=y] && PCI [=y] && (ARM64 || COMPILE_TEST [=y])
>
> Add missing MMU dependency to fix this.
>
> Fixes: a0f25a6bb319 ("drm/hisilicon/hibmc: Allow to be built if COMPILE_TEST is enabled")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/gpu/drm/hisilicon/hibmc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/hisilicon/hibmc/Kconfig b/drivers/gpu/drm/hisilicon/hibmc/Kconfig
> index 073adfe438dd..e5ef1b573732 100644
> --- a/drivers/gpu/drm/hisilicon/hibmc/Kconfig
> +++ b/drivers/gpu/drm/hisilicon/hibmc/Kconfig
> @@ -1,7 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config DRM_HISI_HIBMC
> tristate "DRM Support for Hisilicon Hibmc"
> - depends on DRM && PCI && (ARM64 || COMPILE_TEST)
> + depends on DRM && PCI && (ARM64 || COMPILE_TEST) && MMU
> select DRM_KMS_HELPER
> select DRM_VRAM_HELPER
> select DRM_TTM
>
prev parent reply other threads:[~2022-09-14 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 2:09 YueHaibing
2022-08-23 2:30 ` Randy Dunlap
2022-09-14 6:44 ` YueHaibing [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=584a67fa-cc1d-a30b-ccac-847f717b6d90@huawei.com \
--to=yuehaibing@huawei.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jstultz@google.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=tiantao6@hisilicon.com \
--cc=tzimmermann@suse.de \
--cc=xinliang.liu@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
all inboxes | Powered by JetHome®