Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S943032AbcJSOoh (ORCPT ); Wed, 19 Oct 2016 10:44:37 -0400 Received: from mail.fireflyinternet.com ([109.228.58.192]:59486 "EHLO fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S942017AbcJSOoe (ORCPT ); Wed, 19 Oct 2016 10:44:34 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Date: Wed, 19 Oct 2016 08:26:35 +0100 From: Chris Wilson To: Valentin Rothberg Cc: daniel.vetter@ffwll.ch, LKML Subject: Re: drm/i915: undefined STOP_MACHINE Message-ID: <20161019072635.GH29358@nuc-i3427.alporthouse.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 642 Lines: 18 On Wed, Oct 19, 2016 at 08:27:23AM +0200, Valentin Rothberg wrote: > 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? No. We don't need the select anymore as the core machinery now just works without having to force compilation of the correct code. -Chris -- Chris Wilson, Intel Open Source Technology Centre