Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752627Ab3DGGcs (ORCPT ); Sun, 7 Apr 2013 02:32:48 -0400 Received: from mail-pd0-f178.google.com ([209.85.192.178]:43927 "EHLO mail-pd0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751872Ab3DGGcr (ORCPT ); Sun, 7 Apr 2013 02:32:47 -0400 Date: Sun, 7 Apr 2013 14:32:34 +0800 (CST) From: Xiong Zhou X-X-Sender: zx@M2420 To: linux-kernel@vger.kernel.org, airlied@linux.ie cc: daniel.vetter@ffwll.ch, alan@linux.intel.com, dri-devel@lists.freedesktop.org Subject: [PATCH] drivers/gpu/drm/gma500:fix build failure for 3.9-rc5 Message-ID: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1316 Lines: 34 From: Xiong Zhou This patch fixes build failure of v3.9-rc5. When config ACPI_VIDEO as m, DRM_GMA500 as y, here comes the failure. gma5/600 needs acpi_video just like nouveau. Failure message: drivers/built-in.o: In function `psb_driver_load': kernel-3.9-rc5/drivers/gpu/drm/gma500/psb_drv.c:340: \ undefined reference to `acpi_video_register' make: *** [vmlinux] Error 1 Signed-off-by: Xiong Zhou --- drivers/gpu/drm/gma500/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/gma500/Kconfig b/drivers/gpu/drm/gma500/Kconfig index 1188f0f..d64fc45 100644 --- a/drivers/gpu/drm/gma500/Kconfig +++ b/drivers/gpu/drm/gma500/Kconfig @@ -6,6 +6,7 @@ config DRM_GMA500 select FB_CFB_IMAGEBLIT select DRM_KMS_HELPER select DRM_TTM + select ACPI_VIDEO if ACPI && X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL && INPUT help Say yes for an experimental 2D KMS framebuffer driver for the Intel GMA500 ('Poulsbo') and other Intel IMG based graphics -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/