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
| ||
|
Date: Thu, 18 Feb 2016 16:00:09 -0500 (EST) From: David Miller <davem@...emloft.net> To: arnd@...db.de Cc: oliver@...kum.org, linux-arm-kernel@...ts.infradead.org, linux-usb@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] USB: cdc_subset: only build when one driver is enabled From: Arnd Bergmann <arnd@...db.de> Date: Wed, 17 Feb 2016 23:25:11 +0100 > This avoids a harmless randconfig warning I get when USB_NET_CDC_SUBSET > is enabled, but all of the more specific drivers are not: > > drivers/net/usb/cdc_subset.c:241:2: #warning You need to configure some hardware for this driver > > The current behavior is clearly intentional, giving a warning when > a user picks a configuration that won't do anything good. The only > reason for even addressing this is that I'm getting close to > eliminating all 'randconfig' warnings on ARM, and this came up > a couple of times. > > My workaround is to not even build the module when none of the > configurations are enable. > > Alternatively we could simply remove the #warning (nothing wrong > for compile-testing), turn it into a runtime warning, or > change the Kconfig options into a menu to hide CONFIG_USB_NET_CDC_SUBSET. > > Signed-off-by: Arnd Bergmann <arnd@...db.de> Applied, thanks Arnd.
Powered by blists - more mailing lists