So I decided to fix this with the following follow-up patch. I hope this is the right approach (vs. reverting the commit and instead using a fixed v2 of the original patch). >From 41775d2c8a14873f522667a57b66cfbe119e28a4 Mon Sep 17 00:00:00 2001 From: Nils Holland <nholland@xxxxxxxxx> Date: Tue, 24 Jan 2017 01:36:45 +0100 Subject: [PATCH] drm/amdgpu: Fix error in amdgpu_bo_create_restricted() Remove mistakedly placed ; that prevents the code from compiling. No functional change. Signed-off-by: Nils Holland <nholland at tisys.org> --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c index f71fe41c1c99..89d32131e3f5 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c @@ -377,7 +377,7 @@ int amdgpu_bo_create_restricted(struct amdgpu_device *adev, #warning Please enable CONFIG_MTRR and CONFIG_X86_PAT for better performance \ thanks to write-combining - if (bo->flags & AMDGPU_GEM_CREATE_CPU_GTT_USWC;) + if (bo->flags & AMDGPU_GEM_CREATE_CPU_GTT_USWC) DRM_INFO_ONCE("Please enable CONFIG_MTRR and CONFIG_X86_PAT for " "better performance thanks to write-combining\n"); bo->flags &= ~AMDGPU_GEM_CREATE_CPU_GTT_USWC; -- 2.11.0 Greetings Nils