[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1412372683-2003-5-git-send-email-mcgrof@do-not-panic.com>
Date: Fri, 3 Oct 2014 14:44:40 -0700
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: gregkh@...uxfoundation.org, dmitry.torokhov@...il.com,
tiwai@...e.de, tj@...nel.org, arjan@...ux.intel.com
Cc: teg@...m.no, rmilasan@...e.com, werner@...e.com, oleg@...hat.com,
hare@...e.com, bpoirier@...e.de, santosh@...lsio.com,
pmladek@...e.cz, dbueso@...e.com, mcgrof@...e.com,
linux-kernel@...r.kernel.org,
Doug Thompson <dougthompson@...ssion.com>,
Borislav Petkov <bp@...en8.de>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
linux-edac@...r.kernel.org
Subject: [PATCH v2 4/7] amd64_edac: enforce synchronous probe
From: "Luis R. Rodriguez" <mcgrof@...e.com>
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.
Cc: Tejun Heo <tj@...nel.org>
Cc: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Doug Thompson <dougthompson@...ssion.com>
Cc: Borislav Petkov <bp@...en8.de>
Cc: Mauro Carvalho Chehab <m.chehab@...sung.com>
Cc: linux-edac@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Signed-off-by: Luis R. Rodriguez <mcgrof@...e.com>
---
drivers/edac/amd64_edac.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
index f8bf000..dc997ae 100644
--- a/drivers/edac/amd64_edac.c
+++ b/drivers/edac/amd64_edac.c
@@ -2872,6 +2872,7 @@ static struct pci_driver amd64_pci_driver = {
.probe = probe_one_instance,
.remove = remove_one_instance,
.id_table = amd64_pci_table,
+ .driver.sync_probe = true,
};
static void setup_pci_device(void)
--
2.1.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists