From: Sasha Levin Subject: Re: [PATCH v2 3/3] drm/mgag200: Add workaround for HW that does not support 'startadd' Date: Thu, 28 Nov 2019 14:23:36 +0000 Message-ID: <20191128142337.1B32A217F5@mail.kernel.org> References: <20191126101529.20356-4-tzimmermann@suse.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1397655989==" Return-path: Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by gabe.freedesktop.org (Postfix) with ESMTPS id 7241F6E830 for ; Thu, 28 Nov 2019 14:23:37 +0000 (UTC) In-Reply-To: <20191126101529.20356-4-tzimmermann@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Sasha Levin , Thomas Zimmermann , airlied@redhat.com, daniel@ffwll.ch, john.p.donnelly@oracle.com Cc: =?UTF-8?Q?=2C=20stable=40vger=2Ekernel=2E?= List-Id: dri-devel@lists.freedesktop.org --===============1397655989== Content-Type: text/plain Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 81da87f63a1e ("drm: Replace drm_gem_vram_push_to_system() with kunmap + unpin"). The bot has tested the following trees: v5.3.13. v5.3.13: Build failed! Errors: drivers/gpu/drm/mgag200/mgag200_drv.c:104:18: error: ‘drm_vram_mm_debugfs_init’ undeclared here (not in a function); did you mean ‘drm_client_debugfs_init’? NOTE: The patch will not be queued to stable trees until it is upstream. How should we proceed with this patch? -- Thanks, Sasha --===============1397655989== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1397655989==--