[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#624372: linux-source-2.6.39: Fix warnings for invalid symbol values (now boolean)



On Wed, 2011-04-27 at 22:48 +0200, Sedat Dilek wrote:
> Package: linux-source-2.6.39
> Version: 2.6.39~rc4-1~experimental.1
> Severity: normal
> Tags: patch
> 
> Hi,
> 
> attached patch against debian-dir from linux-2.6/trunk (r17251) fixes
> these warnings:
> 
> .config:555:warning: symbol value 'm' invalid for LEDS_CLASS
> .config:917:warning: symbol value 'm' invalid for MFD_WM8994
> .config:2292:warning: symbol value 'm' invalid for BT_L2CAP
> .config:2293:warning: symbol value 'm' invalid for BT_SCO

> diff -uprN debian-trunk.orig/config/config debian-trunk/config/config
> --- debian-trunk.orig/config/config  2011-04-27 17:14:59.169280262 +0200
> +++ debian-trunk/config/config       2011-04-27 18:35:33.260507504 +0200
> @@ -800,7 +800,7 @@ CONFIG_MISDN_L1OIP=m
>  ## file: drivers/leds/Kconfig
>  ##
>  CONFIG_NEW_LEDS=y
> -CONFIG_LEDS_CLASS=m
> +CONFIG_LEDS_CLASS=y
>  CONFIG_LEDS_NET48XX=m
>  CONFIG_LEDS_ALIX2=m
>  CONFIG_LEDS_PCA9532=m

I don't understand why this is no longer tristate, and I'm not sure most
Debian systems need it.

> @@ -1383,7 +1383,7 @@ CONFIG_HTC_PASIC3=m
>  CONFIG_TPS65010=m
>  CONFIG_MFD_WM8400=m
>  # CONFIG_MFD_WM8350_I2C is not set
> -CONFIG_MFD_WM8994=m
> +# CONFIG_MFD_WM8994 is not set
>  CONFIG_MFD_PCF50633=m
>  CONFIG_PCF50633_ADC=m
>  CONFIG_PCF50633_GPIO=m

OK.  I think most of these MFD drivers are useless without platform data
anyway.

> @@ -3693,8 +3693,8 @@ CONFIG_BATMAN_ADV=m
>  ## file: net/bluetooth/Kconfig
>  ##
>  CONFIG_BT=m
> -CONFIG_BT_L2CAP=m
> -CONFIG_BT_SCO=m
> +CONFIG_BT_L2CAP=y
> +CONFIG_BT_SCO=y
>  
>  ##
>  ## file: net/bluetooth/bnep/Kconfig

OK.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: