Messages in this thread | | | 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 <> | Date | Mon, 29 Feb 2016 10:51:29 +0200 |
| |
On 26/02/16 19:21, David Miller wrote: > From: Tomi Valkeinen <tomi.valkeinen@ti.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 disagree. Having drivers buildable as modules is always good, even if the normal use case would be to have them as built-in.
> I plan to apply this patch series to my sparc tree as-is.
They are fbdev patches without any dependency to sparc afaics. So let's apply them via fbdev tree.
Tomi
[unhandled content-type:application/pgp-signature] | |