lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Mar 2015 13:10:47 -0400
From:	Tejun Heo <>
To:	Borislav Petkov <>
Cc:	Dmitry Torokhov <>,
	Doug Thompson <>,,,
	Mauro Carvalho Chehab <>,
	Tetsuo Handa <>,
	Olof Johansson <>,
	Arjan van de Ven <>,
	Greg Kroah-Hartman <>,
	"Luis R . Rodriguez" <>
Subject: Re: [PATCH 3/3] EDAC: amd64_edac: decide if driver can load
 successfully early.

On Thu, Mar 19, 2015 at 06:04:17PM +0100, Borislav Petkov wrote:
> On Thu, Mar 19, 2015 at 01:03:39PM -0400, Tejun Heo wrote:
> > Just don't do it. It makes the driver behave differently from others
> > for no good reason. Driver being loaded or not doesn't indicate
> > anything anymore other than the code is loaded and you're adding
> > complexity to just make it more confusing and you don't have good
> > enough technical reasons to justify the deviation. What are you even
> > fighting for?
> Scroll back a couple of messages.

lsmod indicating hardware capability?  Really?  You're just adding
confusion to the mix.  Stop.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists