linux-kernel - Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code,Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc code

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 26 Feb 2016 12:21:12 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	tomi.valkeinen@...com
Cc:	paul.gortmaker@...driver.com, linux-kernel@...r.kernel.org,
	plagnioj@...osoft.com, linux-fbdev@...r.kernel.org,
	sparclinux@...r.kernel.org
Subject: Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular
 sparc
 code,Re: [PATCH 0/3] video/fbdev: avoid module usage in non-modular sparc
 code

From: Tomi Valkeinen <tomi.valkeinen@...com>
Date: Fri, 26 Feb 2016 12:58:00 +0200

> While doing this, did you just go forward removing the module support,
> or did you check if it would be trivial to make the driver build as a
> module? I wouldn't be surprised if in some cases all that would need to
> be done is change the Kconfig's bool to tristate.

I think what he is doing is reasonable, and none of these sparc drivers
have any reason to be built modular.  You need them to have any bootup
console whatsoever, so they have to be built in statically to be
usable at all.

I plan to apply this patch series to my sparc tree as-is.