On Mon, Mar 28, 2011 at 04:29:44PM +0200, Par-Gunnar HJALMDAHL wrote: > > > > > > Not exactly what I had in mind, but probably good enough for a start. > > > This adds a dependency from core code to the staging driver now, > > > which shouldn't be there. I suppose we can add > > > > > > "Clean up device registration path to register the main device from > > board code" > > > > > > to the TODO file. > > > > No, please do not make any core code dependant on a staging driver, > > this > > isn't ok, it needs to be stand-alone, or at the least, the rest of the > > kernel needs to be able to be built with no staging drivers enabled. > > > > thanks, > > > > greg k-h > > But how should I then do this? As I understood it I was told that I should > call an init function, but I was not allowed to add any staging folder > inclusion in the board config makefile. And now I can't do any extern > declaration either. I don't really see how I could do it then. Why can't you add a staging folder inclusion? You could do that, and properly set up your .h file so that if the driver is not built, your code still properly builds and runs. thanks, greg k-h -- 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
