[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150319161241.GL25365@htj.duckdns.org>
Date: Thu, 19 Mar 2015 12:12:41 -0400
From: Tejun Heo <tj@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Doug Thompson <dougthompson@...ssion.com>,
linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Olof Johansson <olof@...om.net>,
Arjan van de Ven <arjan@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Luis R . Rodriguez" <mcgrof@...e.com>
Subject: Re: [PATCH 3/3] EDAC: amd64_edac: decide if driver can load
successfully early.
On Thu, Mar 19, 2015 at 05:01:32PM +0100, Borislav Petkov wrote:
> On Thu, Mar 19, 2015 at 11:55:53AM -0400, Tejun Heo wrote:
> <snip needless schooling on driver core>
>
> > This code is standing in the way of a much more impactful generic
> > driver layer improvement.
>
> So why not mark it as synchronously loading and forget about it?
Isn't that obvious? Because hacks like this are likely to cause other
problems down the road and set bad precedences.
--
tejun
--
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