From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755742AbbCSAtW (ORCPT ); Wed, 18 Mar 2015 20:49:22 -0400 Received: from mail-ig0-f179.google.com ([209.85.213.179]:36275 "EHLO mail-ig0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754880AbbCSAtV (ORCPT ); Wed, 18 Mar 2015 20:49:21 -0400 From: Dmitry Torokhov To: Borislav Petkov , Doug Thompson , Tejun Heo Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, Mauro Carvalho Chehab , Tetsuo Handa , Olof Johansson , Arjan van de Ven , Greg Kroah-Hartman , "Luis R . Rodriguez" Subject: [RFC/RFT] amd64_edac: avoid doing post-probe setup Date: Wed, 18 Mar 2015 17:49:07 -0700 Message-Id: <1426726150-983-1-git-send-email-dmitry.torokhov@gmail.com> X-Mailer: git-send-email 2.2.0.rc0.207.ga3a616c Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While testing asynchronous probing Luis noticed that this driver was failing to initialize. It is happening because the driver tries to check the result of binding, assuming that it is done synchronously, and either abort the loading, or perform some additional setup steps. This series tried to work around it by moving these post-binding steps into probe() to be executed when binding node 0. Untested as I do not have AMD boxes. Thanks! -- Dmitry