From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
Doug Thompson <dougthompson@xmission.com>,
Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Olof Johansson <olof@lixom.net>,
Arjan van de Ven <arjan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Luis R . Rodriguez" <mcgrof@suse.com>
Subject: [RFC/RFT] amd64_edac: avoid doing post-probe setup
Date: Wed, 18 Mar 2015 17:49:07 -0700 [thread overview]
Message-ID: <1426726150-983-1-git-send-email-dmitry.torokhov@gmail.com> (raw)
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
next reply other threads:[~2015-03-19 0:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 0:49 Dmitry Torokhov [this message]
2015-03-19 0:49 ` [PATCH 1/3] EDAC: amd64: stop allocating ecc settings separately Dmitry Torokhov
2015-03-19 0:49 ` [PATCH 2/3] EDAC: amd64_edac: clean up remove_one_instance() Dmitry Torokhov
2015-03-19 0:49 ` [PATCH 3/3] EDAC: amd64_edac: decide if driver can load successfully early Dmitry Torokhov
2015-03-19 9:40 ` Borislav Petkov
2015-03-19 15:29 ` Tejun Heo
2015-03-19 15:35 ` Borislav Petkov
2015-03-19 15:52 ` Dmitry Torokhov
2015-03-19 15:59 ` Borislav Petkov
2015-03-19 16:12 ` Dmitry Torokhov
2015-03-19 16:23 ` Borislav Petkov
2015-03-19 16:33 ` Tejun Heo
2015-03-19 16:45 ` Borislav Petkov
2015-03-19 16:49 ` Tejun Heo
2015-03-19 16:56 ` Borislav Petkov
2015-03-19 17:03 ` Tejun Heo
2015-03-19 17:04 ` Borislav Petkov
2015-03-19 17:10 ` Tejun Heo
2015-03-19 17:15 ` Tejun Heo
2015-03-19 17:27 ` Borislav Petkov
2015-03-19 17:47 ` Tejun Heo
2015-03-19 17:54 ` Borislav Petkov
2015-03-19 18:05 ` Tejun Heo
2015-03-19 16:52 ` Dmitry Torokhov
2015-03-19 17:09 ` Tejun Heo
2015-03-19 15:55 ` Tejun Heo
2015-03-19 16:01 ` Borislav Petkov
2015-03-19 16:12 ` Tejun Heo
2015-03-19 16:57 ` Dmitry Torokhov
2015-03-19 17:22 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1426726150-983-1-git-send-email-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dougthompson@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mchehab@osg.samsung.com \
--cc=olof@lixom.net \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).