Hi David,
2006/6/14, David Brownell [EMAIL PROTECTED]:
On Wednesday 07 June 2006 6:11 am, Franck Bui-Huu wrote:
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent. Therefore it will dead lock.
This patch
On Wednesday 07 June 2006 6:11 am, Franck Bui-Huu wrote:
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent. Therefore it will dead lock.
This patch fixes it and also uses the generic scheduler services
for
ping
Franck Bui-Huu wrote:
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent.
It also uses the generic scheduler function for waiting for an
event.
Signed-off-by: Franck Bui-Huu [EMAIL PROTECTED]
---
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent. Therefore it will dead lock.
This patch fixes it and also uses the generic scheduler services
for waiting for an event.
Signed-off-by: Franck Bui-Huu [EMAIL
Greg KH wrote:
On Tue, Jun 06, 2006 at 10:31:51AM +0200, Franck Bui-Huu wrote:
ping
I was waiting for an ack from the original author of this code. Al, any
comments?
well, thinking more about it, I think the original author wrote its
own wait_event_xxx macros to test the event condition
When closing the device, the driver acquires/release twice the
port lock before/after waiting for the data to be completely
sent.
It also uses the generic scheduler function for waiting for an
event.
Signed-off-by: Franck Bui-Huu [EMAIL PROTECTED]
---
well I'm probably missing
