mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "wenst@chromium.org" <wenst@chromium.org>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>,
	"simona@ffwll.ch" <simona@ffwll.ch>,
	"mripard@kernel.org" <mripard@kernel.org>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"airlied@gmail.com" <airlied@gmail.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/mediatek: Drop dependency on ARM
Date: Wed, 30 Oct 2024 03:30:34 +0000	[thread overview]
Message-ID: <d9177ba80fc78b1f74dc54260c0c43440ec5a804.camel@mediatek.com> (raw)
In-Reply-To: <20241029111309.737263-1-wenst@chromium.org>

Hi, Chen-yu:

On Tue, 2024-10-29 at 19:13 +0800, Chen-Yu Tsai wrote:
> External email : Please do not click links or open attachments until you have verified the sender or the content.
> 
> 
> The recent attempt to make the MediaTek DRM driver build for non-ARM
> compile tests made the driver unbuildable for arm64 platforms. Since
> this is used on both ARM and arm64 platforms, just drop the dependency
> on ARM.

Reviewed-by: CK Hu <ck.hu@mediatek.com>

I find this days ago, but I don't know there is someone who apply it.
Let this patch go through drm-misc tree which already has the bug patch.

Regards,
CK


> 
> Fixes: d2db0b8fd70b ("drm/mediatek: Allow build with COMPILE_TEST=y")
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
> ---
> It looks like the culprit commit was merged through the drm-misc tree.
> So please merge this on top ASAP.
> 
>  drivers/gpu/drm/mediatek/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/mediatek/Kconfig b/drivers/gpu/drm/mediatek/Kconfig
> index 2e0e7c4079b6..f496e6cfdfe0 100644
> --- a/drivers/gpu/drm/mediatek/Kconfig
> +++ b/drivers/gpu/drm/mediatek/Kconfig
> @@ -2,7 +2,7 @@
>  config DRM_MEDIATEK
>         tristate "DRM Support for Mediatek SoCs"
>         depends on DRM
> -       depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST
> +       depends on ARCH_MEDIATEK || COMPILE_TEST
>         depends on COMMON_CLK
>         depends on HAVE_ARM_SMCCC || COMPILE_TEST
>         depends on OF
> --
> 2.47.0.163.g1226f6d8fa-goog
> 

  reply	other threads:[~2024-10-30  3:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 11:13 Chen-Yu Tsai
2024-10-30  3:30 ` CK Hu (胡俊光) [this message]
2024-10-30  8:25   ` mripard
2024-10-30  8:48     ` CK Hu (胡俊光)
2024-10-30  8:52       ` Chen-Yu Tsai
2024-10-31  9:30         ` mripard
2024-10-31  9:34           ` Chen-Yu Tsai
2024-11-01  7:33 ` Chen-Yu Tsai

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=d9177ba80fc78b1f74dc54260c0c43440ec5a804.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=airlied@gmail.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=ville.syrjala@linux.intel.com \
    --cc=wenst@chromium.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®