linux-kernel - Re: [PATCH] i2c: nforce2: Use IS_ENABLED() instead of checking for built-in or 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] [day] [month] [year] [list]

Message-ID: <20160426213834.GJ4587@katana>
Date:	Tue, 26 Apr 2016 23:38:35 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Javier Martinez Canillas <javier@....samsung.com>
Cc:	linux-kernel@...r.kernel.org, Jean Delvare <jdelvare@...e.com>,
	linux-i2c@...r.kernel.org
Subject: Re: [PATCH] i2c: nforce2: Use IS_ENABLED() instead of checking for
 built-in or module

On Tue, Apr 26, 2016 at 01:22:33PM -0400, 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.
> 
> Signed-off-by: Javier Martinez Canillas <javier@....samsung.com>
> 

Applied to for-next, thanks!


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