On Mon, Nov 24, 2008 at 01:52:51PM -0800, Stephen Hemminger wrote: > On Mon, 24 Nov 2008 22:00:28 +0100 > Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > > On Mon, Nov 24, 2008 at 04:38:44PM +1100, Stephen Rothwell wrote: > > > On Sun, 23 Nov 2008 21:23:39 -0800 (PST) David Miller <davem@xxxxxxxxxxxxx> wrote: > > > > > > > > Probably it didn't build for some obscure reason a long time > > > > ago. I'll try to get it turned back on, but better is to > > > > bring it in via drivers/Kconfig don't you think? :-) > > > > > > Only if you test build all the other architectures that currently don't > > > include it. :-) > > > > Stephen, could I ask you to try to do so? > > You have the infrastructure to do it. > > > > I would love to see any simplification of the nightmare > > of Kconfig files we have. > > > > > > I have only: arm, x86, sparc sparc64, alpha here so that > > does not give any decent enough coverage. > > > > And my current Linux box is a Pentium 850 MHz so it would take > > forever... > > > > Sam > > I will try and run 'make all modconfig' on x86, I don't have volunteer > time to do cross build of all architectures. But isn't the purpose > of linux-next to find/fix these things. If linux-net has to be perfect > every minute then there is no purpose in having it. Hi Stephen - it was Stepehn Rothwell I had in mind when I wrote the above :-) Anyway - I can see that only "cris m68k parisc s390 sparc sparc64 um" lacks the include of drivers/scsi/pcmcia/Kconfig. So I will try to add it to drivers/Kconfig in my tree and see it -next blows up. I will wait until next -next as I want to see my current pending patches there in a clean run first. Sam > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
