On Fri, Feb 25, 2011 at 11:15:00AM -0800, David Miller wrote: > From: David Miller <davem@xxxxxxxxxxxxx> > Date: Thu, 24 Feb 2011 22:43:44 -0800 (PST) > > Pulled, thanks a lot John. > > John a few things: > > 1) I had to add some vmalloc.h includes to fix the build on sparc64, > see commit b08cd667c4b6641c4d16a3f87f4550f81a6d69ac in net-next-2.6 I have a patch in my tree for that -- seems they hit it on ARM as well. > 2) Something is screwey with the bluetooth config options now. > > I have an allmodconfig tree, and when I run "make oldconfig" after > this pull, BT_L2CAP and BT_SCO both prompt me, claiming that they > can only be built statically. > > 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 > > First, what the heck is going on here? Second, why the heck can't these > non-trivial pieces of code be built modular any more? > > You can't make something "bool", have it depend on something that > might be modular, and then build it into what could in fact be a > module. That's exactly what the bluetooth stuff seems to be doing > now. > > I suspect commit 642745184f82688eb3ef0cdfaa4ba632055be9af > > Thanks. Sorry, I overlooked that. Hopefully Gustavo will figure it out quickly. Thanks, John -- 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
