[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXv+5EWyGGKYo+NNQ3Ykd3QUUO2cOManSnhZQaVhhCnupNx=Q@mail.gmail.com>
Date: Wed, 30 Oct 2024 16:52:17 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: CK Hu (胡俊光) <ck.hu@...iatek.com>
Cc: "mripard@...nel.org" <mripard@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
"chunkuang.hu@...nel.org" <chunkuang.hu@...nel.org>, "tzimmermann@...e.de" <tzimmermann@...e.de>,
"simona@...ll.ch" <simona@...ll.ch>,
"ville.syrjala@...ux.intel.com" <ville.syrjala@...ux.intel.com>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"maarten.lankhorst@...ux.intel.com" <maarten.lankhorst@...ux.intel.com>, "airlied@...il.com" <airlied@...il.com>
Subject: Re: [PATCH] drm/mediatek: Drop dependency on ARM
On Wed, Oct 30, 2024 at 4:48 PM CK Hu (胡俊光) <ck.hu@...iatek.com> wrote:
>
> On Wed, 2024-10-30 at 09:25 +0100, mripard@...nel.org wrote:
> > On Wed, Oct 30, 2024 at 03:30:34AM +0000, CK Hu (胡俊光) wrote:
> > > 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@...iatek.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.
> >
> > If you are ok with this patch, why didn't you apply it yourself?
> >
> > I think that's very much the expectation, so it's probably took a while to merge.
>
> That's ok for me to apply it if drm-misc has no plan to apply it.
I'm confused. The culprit patch is already in drm-misc. So this one has
to go in drm-misc as well.
I can try to apply it to drm-misc myself, or have a colleague assist with
that. I'll let it sit for another day in case anyone has something to say
about it.
ChenYu
Powered by blists - more mailing lists