Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
c4c3ce8e
Commit
c4c3ce8e
authored
Sep 08, 2004
by
Greg Kroah-Hartman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
USB: fix usb_unlink_urb() usage in cyberjack driver
Signed-off-by:
Greg Kroah-Hartman
<
greg@kroah.com
>
parent
2e7970b7
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
drivers/usb/serial/cyberjack.c
drivers/usb/serial/cyberjack.c
+3
-3
No files found.
drivers/usb/serial/cyberjack.c
View file @
c4c3ce8e
...
...
@@ -149,7 +149,7 @@ static void cyberjack_shutdown (struct usb_serial *serial)
dbg
(
"%s"
,
__FUNCTION__
);
for
(
i
=
0
;
i
<
serial
->
num_ports
;
++
i
)
{
usb_
unlink_urb
(
serial
->
port
[
i
]
->
interrupt_in_urb
);
usb_
kill_urb
(
serial
->
port
[
i
]
->
interrupt_in_urb
);
/* My special items, the standard routines free my urbs */
kfree
(
usb_get_serial_port_data
(
serial
->
port
[
i
]));
usb_set_serial_port_data
(
serial
->
port
[
i
],
NULL
);
...
...
@@ -189,8 +189,8 @@ static void cyberjack_close (struct usb_serial_port *port, struct file *filp)
if
(
port
->
serial
->
dev
)
{
/* shutdown any bulk reads that might be going on */
usb_
unlink_urb
(
port
->
write_urb
);
usb_
unlink_urb
(
port
->
read_urb
);
usb_
kill_urb
(
port
->
write_urb
);
usb_
kill_urb
(
port
->
read_urb
);
}
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment