From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH] Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig Date: Wed, 02 Mar 2011 21:54:33 -0800 (PST) Message-ID: <20110302.215433.39198854.davem@davemloft.net> References: <20110226013639.GA2166@joana> <1298684485-3081-1-git-send-email-padovan@profusion.mobi> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org, linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org Return-path: In-Reply-To: <1298684485-3081-1-git-send-email-padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org> Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org From: "Gustavo F. Padovan" Date: Fri, 25 Feb 2011 22:41:25 -0300 > If we want something "bool" built-in in something "tristate" it can't > "depend on" the tristate config option. > > Report by DaveM: > > I give it 'y' just to make it happen, for both, and afterways no > matter how many times I rerun "make oldconfig" I keep seeing things > like this in my build: > > scripts/kconfig/conf --silentoldconfig Kconfig > include/config/auto.conf:986:warning: symbol value 'm' invalid for BT_SCO > include/config/auto.conf:3156:warning: symbol value 'm' invalid for BT_L2CAP > > Reported-by: David S. Miller > Signed-off-by: Gustavo F. Padovan I think this approach is fine since it mirrors what we use in other similar situations. I am assuming this patch will propagate via bluetooth --> wireless --> me. Thanks.