linux-kernel - Re: [PATCH] spi: Add builtin_spi_driver() to avoid registration boilerplate

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:	Wed, 16 Dec 2015 13:23:57 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: Add builtin_spi_driver() to avoid registration
 boilerplate

On Sun, Dec 13, 2015 at 03:53:57PM -0500, Paul Gortmaker wrote:

> Here we use that support and extend it to SPI driver registration, so where
> a driver is clearly non-modular and builtin-only, we can register it in a
> similar fashion.  Existing code that is clearly non-modular can be updated
> with the simple mapping of

>   module_spi_driver(...)  ---> builtin_spi_driver(...)

> We've essentially cloned the former to make the latter, and taken out the
> remove/module_exit parts since those never get used in a non-modular build
> of the code.

Why would it be sensible to have a SPI driver that can't be built as a
module?

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)