>> > >> Perhaps this is a bad example? It seems like the "common layer" > >> sections that are "cross-OS" shouldn't contain any Linux specific code > at all. > > > > I think the implication is that the cross-OS parts are coded, as it > > happens, in the linux coding style, using linux functions, but then a > > Windows layer maps these to Windows specific functions. > > Correct. > > Jeff > > > [Atul] I think we are close, for example, memcpy API in the stack is osi_memcpy(), which translates to memcpy() on Linux and ScsiPortMoveMemory() on windows. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
