From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754744AbbCSQTd (ORCPT ); Thu, 19 Mar 2015 12:19:33 -0400 Received: from mail-vc0-f172.google.com ([209.85.220.172]:51972 "EHLO mail-vc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751451AbbCSQTb (ORCPT ); Thu, 19 Mar 2015 12:19:31 -0400 Date: Thu, 19 Mar 2015 12:19:27 -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: <20150319161927.GM25365@htj.duckdns.org> References: <20150318195141.GD25365@htj.duckdns.org> <20150318202605.GI11485@dtor-ws> <20150318210226.GE25365@htj.duckdns.org> <20150318214126.GJ11485@dtor-ws> <20150318215028.GF25365@htj.duckdns.org> <20150318221530.GK11485@dtor-ws> <20150318232401.GG25365@htj.duckdns.org> <20150319002619.GM11485@dtor-ws> <20150319154141.GJ25365@htj.duckdns.org> <20150319160146.GB30732@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150319160146.GB30732@dtor-ws> 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 Hello, On Thu, Mar 19, 2015 at 09:01:46AM -0700, Dmitry Torokhov wrote: > I think that would be the goal, yes, but I think we'd need some "trial" > period before we can do that: I need to look into at least serial and > regulators to make it work (not even considering any userspace). We are > definitely not ready just yet and that is why I have a whitelist: there > are classes of devices that all userspaces learned to deal with long ago > and we can make them not stall boot right now. Yeah, as I wrote before, as long as there's a plan and push to finish the conversion, it's fine. I'm just worried that this might rot in the grey area. Can we please update the patches so that it's clear that the whitelist is a temporary measure both in the description and code? Thanks. -- tejun