Re: [PATCH v3] init: staging: Fix missing warning/taint on builtin code

On Sat, Jul 06, 2024 at 12:15:01AM -0300, Ágatha Isabelle Chris Moreira Guedes wrote: > Fix the absence of warning message and kernel tainting when initializing > drivers from the `drivers/staging` subtree from initcalls (when > configured as built-in). > > When such a driver is built as module

Re: [PATCH v3] init: staging: Fix missing warning/taint on builtin code

Hello, On Sat, Jul 06, 2024 at 12:15:01AM -0300, Ágatha Isabelle Chris Moreira Guedes wrote: > Fix the absence of warning message and kernel tainting when initializing > drivers from the `drivers/staging` subtree from initcalls (when > configured as built-in). > > When such a driver is built as

Re: [PATCH v3] init: staging: Fix missing warning/taint on builtin code

Thanks! Acked-by: Dan Carpenter regards, dan carpenter

[PATCH v3] init: staging: Fix missing warning/taint on builtin code

Fix the absence of warning message and kernel tainting when initializing drivers from the `drivers/staging` subtree from initcalls (when configured as built-in). When such a driver is built as module and the module is loaded, the `load_module()` function taints the kernel to signal code of