diff options
| author | Kay Sievers <kay.sievers@vrfy.org> | 2012-01-17 18:12:10 +0100 |
|---|---|---|
| committer | Kay Sievers <kay.sievers@vrfy.org> | 2012-01-17 18:12:10 +0100 |
| commit | bf85160ada0dd2f21405fdbbee717cc0e329925b (patch) | |
| tree | 335392a20eccc9252fb58bbd39239e05e94ce27a | |
| parent | b4e0af938d92107de48ca520045121e482e63cec (diff) | |
| download | patches-bf85160ada0dd2f21405fdbbee717cc0e329925b.tar.gz | |
fix typos in commit log
| -rw-r--r-- | udlfb.patch | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/udlfb.patch b/udlfb.patch index 200aaf4..ddcb393 100644 --- a/udlfb.patch +++ b/udlfb.patch @@ -1,5 +1,5 @@ From: Kay Sievers <kay.sievers@vrfy.org> -Subject: udlfb: remove sysfs frambuffer device with USB .disconnect() +Subject: udlfb: remove sysfs framebuffer device with USB .disconnect() The USB graphics card driver delays the unregistering of the framebuffer device to a workqueue, which breaks the userspace visible remove event @@ -7,8 +7,8 @@ sequence. The framebuffer device is a direct child of the USB interface which is removed immedeately after the USB .disconnect() callback. But the fb device -stay around until its final cleanup, at a time where all the parent devices -are already gone. +in /sys stays around until its final cleanup, at a time where all the parent +devices have been removed already. To work around that, we remove the sysfs fb device directly in the USB .disconnect() callback and leave only the cleanup of the internal fb |