diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2016-02-17 23:25:11 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-02-18 21:59:45 +0100 |
| commit | f3bb23764fac042d189129d485d3a9246cb777da (patch) | |
| tree | 65aa62f8cc3d10a2ef1c4ad757afb8e125a5e302 /net | |
| parent | vxlan: do not use fdb in metadata mode (diff) | |
| download | linux-f3bb23764fac042d189129d485d3a9246cb777da.tar.xz linux-f3bb23764fac042d189129d485d3a9246cb777da.zip | |
USB: cdc_subset: only build when one driver is enabled
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@arndb.de>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions