On Wed, Mar 02, 2011 at 09:54:33PM -0800, David Miller wrote: > From: "Gustavo F. Padovan" <padovan@xxxxxxxxxxxxxx> > 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 <davem@xxxxxxxxxxxxx> > > Signed-off-by: Gustavo F. Padovan <padovan@xxxxxxxxxxxxxx> > > 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. Yes, I have it queued. -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
