aboutsummaryrefslogtreecommitdiff
path: root/Documentation/Intel-IOMMU.txt
diff options
context:
space:
mode:
authorMatt LaPlante2008-07-25 19:45:33 -0700
committerLinus Torvalds2008-07-26 12:00:06 -0700
commitd91958815d214ea365b98cbff6215383897edcb6 (patch)
treea50416a04c9ae84c4242dbec62d8f211d97ea4d2 /Documentation/Intel-IOMMU.txt
parent19fd6231279be3c3bdd02ed99f9b0eb195978064 (diff)
Documentation cleanup: trivial misspelling, punctuation, and grammar corrections.
Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/Intel-IOMMU.txt')
-rw-r--r--Documentation/Intel-IOMMU.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/Intel-IOMMU.txt b/Documentation/Intel-IOMMU.txt
index c2321903aa09..21bc416d887e 100644
--- a/Documentation/Intel-IOMMU.txt
+++ b/Documentation/Intel-IOMMU.txt
@@ -48,7 +48,7 @@ IOVA generation is pretty generic. We used the same technique as vmalloc()
but these are not global address spaces, but separate for each domain.
Different DMA engines may support different number of domains.
-We also allocate gaurd pages with each mapping, so we can attempt to catch
+We also allocate guard pages with each mapping, so we can attempt to catch
any overflow that might happen.
@@ -112,4 +112,4 @@ TBD
- For compatibility testing, could use unity map domain for all devices, just
provide a 1-1 for all useful memory under a single domain for all devices.
-- API for paravirt ops for abstracting functionlity for VMM folks.
+- API for paravirt ops for abstracting functionality for VMM folks.