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
9a4d5a43
Commit
9a4d5a43
authored
Feb 03, 2004
by
Greg Kroah-Hartman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] dmapool: Remove sentance in documentation that is now false on 2.6
parent
de56fa21
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
3 deletions
+1
-3
Documentation/DMA-API.txt
Documentation/DMA-API.txt
+1
-3
No files found.
Documentation/DMA-API.txt
View file @
9a4d5a43
...
@@ -131,9 +131,7 @@ were returned when that routine allocated the memory being freed.
...
@@ -131,9 +131,7 @@ were returned when that routine allocated the memory being freed.
The pool destroy() routines free the resources of the pool. They must be
The pool destroy() routines free the resources of the pool. They must be
called in a context which can sleep. Make sure you've freed all allocated
called in a context which can sleep. Make sure you've freed all allocated
memory back to the pool before you destroy it. While pci_pool_destroy()
memory back to the pool before you destroy it.
may not be called in interrupt context, it's perfectly safe to do that with
dma_pool_destroy().
Part Ic - DMA addressing limitations
Part Ic - DMA addressing limitations
...
...
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