Originally Posted by netllama
I'm not sure what kind of reply you're seeking. I commented on the progress of this issue 2 days ago.
I'm seeking a reply that tells us, with some sort of official statement, that you're not shelving the bug but are actively seeking to fix it and that it will
be fixed in an upcoming release (i.e. the next release) of the driver.