Re: [PATCH 12/15] sis900: use IS_ENABLED() instead of checking for built-in or module

On 12 September 2016 16:03:43 CEST, Javier Martinez Canillas wrote: >The IS_ENABLED() macro checks if a Kconfig symbol has been enabled >either >built-in or as a module, use that macro instead of open coding the >same. > >Using the macro makes the code more readable by

Re: [PATCH 12/15] sis900: use IS_ENABLED() instead of checking for built-in or module

On 12 September 2016 16:03:43 CEST, Javier Martinez Canillas wrote: >The IS_ENABLED() macro checks if a Kconfig symbol has been enabled >either >built-in or as a module, use that macro instead of open coding the >same. > >Using the macro makes the code more readable by helping abstract away

[PATCH 12/15] sis900: use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Using the macro makes the code more readable by helping abstract away some of the Kconfig built-in and module enable details. Signed-off-by: Javier

[PATCH 12/15] sis900: use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Using the macro makes the code more readable by helping abstract away some of the Kconfig built-in and module enable details. Signed-off-by: Javier