linux-kernel - Re: [PATCH v2] HID: 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: <alpine.LNX.2.00.1608021641570.22028@cbobk.fhfr.pm>
Date:	Tue, 2 Aug 2016 16:42:06 +0200 (CEST)
From:	Jiri Kosina <jikos@...nel.org>
To:	Javier Martinez Canillas <javier@....samsung.com>
cc:	linux-kernel@...r.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@...hat.com>,
	linux-input@...r.kernel.org
Subject: Re: [PATCH v2] HID: use IS_ENABLED() instead of checking for built-in
 or module

On Thu, 21 Jul 2016, 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 some
> of the Kconfig built-in and module enable details.

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs