linux-kernel - Re: Problem with commit: x86, iosf: Make IOSF driver modular and usable by more drivers

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 25 Aug 2014 20:02:15 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	Fejes József <jozsef.fejes@...il.com>,
	linux-kernel@...r.kernel.org, linux-stable@...r.kernel.org,
	"David E. Box" <david.e.box@...ux.intel.com>
Subject: Re: Problem with commit: x86, iosf: Make IOSF driver modular and
 usable by more drivers

> David, any other suggestions?
> Why can't the users of IOSF_MBI just select it?  That's what many other
> drivers do when they need to be sure that some functionality is present.

I think the obvious problem is that most users of IOSF_MBI are
non-obvious and there will be many of them over time.
> 
> I'm surprised that someone else (e.g. Linus) has not complained about the
> 'default m' for this driver.

That's certainly wrong, but drivers that use it should probably
auto-select it or we will get a billion bug reports asking why graphics
doesn't work etc 

Alan
--
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/