> > > Using one or the other internally is fine (we don't care what you do), > > > but we want to see memcpy(). By the way, the documentation I found > for > > > ScsiPortMoveMemory() seems to indicate that it's memmove(), not > memcpy(). > > > Mapping memcpy() to ScsiPortMoveMemory() is fine ... but you can't > > > realiably go the other way. > > [Atul] It's actually memcpy(),http://msdn.microsoft.com/en- > us/library/ms805434.aspx > > No, it's memmove(). "The (ReadBuffer + Length) can overlap the area > pointed to by WriteBuffer." [Atul] Look, you are already figuring out possible issues with the source code without it being out yet :-). Thanks everyone for your inputs so far! Atul -- 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
