On Thu, Oct 31, 2024 at 5:30 PM mripard@xxxxxxxxxx <mripard@xxxxxxxxxx> wrote: > > On Wed, Oct 30, 2024 at 04:52:17PM +0800, Chen-Yu Tsai wrote: > > On Wed, Oct 30, 2024 at 4:48 PM CK Hu (胡俊光) <ck.hu@xxxxxxxxxxxx> wrote: > > > > > > On Wed, 2024-10-30 at 09:25 +0100, mripard@xxxxxxxxxx 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@xxxxxxxxxxxx> > > > > > > > > > > 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. > > Sorry, I was under the assumption that CK had drm-misc commit rights? It > should go through drm-misc indeed. CK has always maintained a separate tree on git.kernel.org, so I don't know if drm-misc commit rights were ever granted? ChenYu
