"Hemanth V" <hemanthv@xxxxxx> writes: >> >> A Santosh suggested, you need to break this up into parts that are >> OMAP specific (arch/arm/*) and parts that go via the SPI subsystem >> (drivers/spi/*.) If doing this breaks your series, then fix it > > But then that would cause a problem, we will not be able to > use arch/arm/plat-omap/include/mach/mcspi.h and will need to redefine those > variables in omap2_mcspi.c which obviously is not the preferred way. Anything shared between the driver and the arch code should go into <mach/mcspi.h>, this way the arch code always compiles. For the driver code, when it's submitted upstream, you state that it has a dependency on the arch code if it is not yet upstream. The point is to separate out the arch code and get it submitted/merged asap so driver code has a smooth path. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
