From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756158AbbCRQ4X (ORCPT ); Wed, 18 Mar 2015 12:56:23 -0400 Received: from mail-vc0-f174.google.com ([209.85.220.174]:34334 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756024AbbCRQ4W (ORCPT ); Wed, 18 Mar 2015 12:56:22 -0400 Date: Wed, 18 Mar 2015 12:56:18 -0400 From: Tejun Heo To: Dmitry Torokhov Cc: Greg Kroah-Hartman , "Luis R . Rodriguez" , linux-kernel@vger.kernel.org, Arjan van de Ven , Rusty Russell , Olof Johansson , Tetsuo Handa Subject: Re: [PATCH 6/8] amd64_edac: enforce synchronous probe Message-ID: <20150318165618.GB21564@htj.duckdns.org> References: <1421451197-19723-1-git-send-email-dmitry.torokhov@gmail.com> <1421451197-19723-7-git-send-email-dmitry.torokhov@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1421451197-19723-7-git-send-email-dmitry.torokhov@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 16, 2015 at 03:33:15PM -0800, Dmitry Torokhov wrote: > From: Luis R. Rodriguez > > While testing asynchronous PCI probe on this driver I noticed it failed > so enforce just synchronouse probe for now. Asynchronous probe is not > used by default and requires userepace intervention. Patches for its > support will be merged later. > > The reason async probe fails is that the init call for this driver > relies on probe to have finished for at least one device. This needs to > be addressed before enabling async probe. I'm still kinda uncomfortable with this both white and black list behavior. If we're gonna do this, let's please drop the debug options and build proper blacklists; otherwise, this will never be complete and we're gonna left with the in-between situation forever. Thanks. -- tejun