> I was told that the driver was ready for merging, it was just going > through a different tree and would be in .31. > > > NAK > > Why NAK a driver that is ready to be merged now? When the MRST stuff > goes in, then this one will be available to be used instantly. I've not seen any of the MRST core code even submitted to linux-kernel. In addition that core code may well itself get a NAK or have to go for rewrite/repair in which case your patch is left dangling. The right way to do this is to sort out the MRST submissions in their own proper order as one series which is a point I've already made to the right people. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
