Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756434AbcJSG2D (ORCPT ); Wed, 19 Oct 2016 02:28:03 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:35430 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750741AbcJSG1z (ORCPT ); Wed, 19 Oct 2016 02:27:55 -0400 MIME-Version: 1.0 From: Valentin Rothberg Date: Wed, 19 Oct 2016 08:27:23 +0200 Message-ID: Subject: drm/i915: undefined STOP_MACHINE To: chris@chris-wilson.co.uk, daniel.vetter@ffwll.ch Cc: LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 491 Lines: 16 Dear Chris, your commit 9f267eb8d2ea ("drm/i915: Stop the machine whilst capturing the GPU crash dump") has popped up in today's linux-next and adds a select from DRM_I915 on STOP_MACHINE, which is not defined anywhere in Kconfig. STOP_MACHINE has been removed a while ago (see https://lkml.org/lkml/2015/11/19/133). I assume that HOTPLUG_CPU could be used? I detected the issue with scripts/checkkconfigsymbols.py by diffing yesterday's and today's linux-next. Best regards, Valentin