linux-kernel - Re: [PATCH 0/6] staging: android: allow building some drivers as a module

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:	Mon, 10 Aug 2015 23:10:37 +0300
From:	Mike Rapoport <mike.rapoport@...il.com>
To:	Greg Kroah-Hartman <greg@...ah.com>
Cc:	Brian Swetland <swetland@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] staging: android: allow building some drivers as a module

On Mon, Aug 10, 2015 at 6:38 PM, Greg Kroah-Hartman <greg@...ah.com> wrote:
> On Mon, Aug 10, 2015 at 09:24:15AM +0300, Mike Rapoport wrote:
>> Hi,
>>
>> These patches enable building of timed_gpio, sync* and ashmem as a module
>
> Why do you want to do this?

Apparently I've misread "- make sure things build as modules properly"
line in drivers/staging/android/TODO...
My bad.

> Does it ever make sense to do this type of
> thing for your kernel?  What does changing these to modules enable you
> to do differently?
>
> As it is, I think the code should stay non-modular.
>
> thanks,
>
> greg k-h



-- 
Sincerely yours,
Mike.
--
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/