Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
linux-davinci
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
linux
linux-davinci
Commits
b5f61ab9
Commit
b5f61ab9
authored
Sep 23, 2008
by
David S. Miller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
usbatm: Use skb_queue_walk_safe() instead of by-hand implementation.
Signed-off-by:
David S. Miller
<
davem@davemloft.net
>
parent
47a227db
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
drivers/usb/atm/usbatm.c
drivers/usb/atm/usbatm.c
+2
-3
No files found.
drivers/usb/atm/usbatm.c
View file @
b5f61ab9
...
...
@@ -640,14 +640,13 @@ static void usbatm_cancel_send(struct usbatm_data *instance,
atm_dbg
(
instance
,
"%s entered
\n
"
,
__func__
);
spin_lock_irq
(
&
instance
->
sndqueue
.
lock
);
for
(
skb
=
instance
->
sndqueue
.
next
,
n
=
skb
->
next
;
skb
!=
(
struct
sk_buff
*
)
&
instance
->
sndqueue
;
skb
=
n
,
n
=
skb
->
next
)
skb_queue_walk_safe
(
&
instance
->
sndqueue
,
skb
,
n
)
{
if
(
UDSL_SKB
(
skb
)
->
atm
.
vcc
==
vcc
)
{
atm_dbg
(
instance
,
"%s: popping skb 0x%p
\n
"
,
__func__
,
skb
);
__skb_unlink
(
skb
,
&
instance
->
sndqueue
);
usbatm_pop
(
vcc
,
skb
);
}
}
spin_unlock_irq
(
&
instance
->
sndqueue
.
lock
);
tasklet_disable
(
&
instance
->
tx_channel
.
tasklet
);
...
...
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