summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-08-25 20:46:10 +0200
committerMichael Witten <mfwitten@gmail.com>2011-08-29 21:30:53 +0200
commit8814630f0b59421e558f4403b79f5dc3a025a386 (patch)
treedc010afe533ca552bb5eb7e3106866b27002c066 /Documentation
parentDocBook/drm: Clearer wording with `for consumption by' (diff)
downloadlinux-8814630f0b59421e558f4403b79f5dc3a025a386.tar.xz
linux-8814630f0b59421e558f4403b79f5dc3a025a386.zip
DocBook/drm: Insert missing `that'
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/DocBook/drm.tmpl4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 33290e3e3ffa..25e0f460a973 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -321,10 +321,10 @@
<para>
Finding &amp; mapping resources is fairly straightforward. The
DRM wrapper functions, drm_get_resource_start() and
- drm_get_resource_len() may be used to find BARs on the given
+ drm_get_resource_len(), may be used to find BARs on the given
drm_device struct. Once those values have been retrieved, the
driver load function can call drm_addmap() to create a new
- mapping for the BAR in question. Note you probably want a
+ mapping for the BAR in question. Note that you probably want a
drm_local_map_t in your driver private structure to track any
mappings you create.
<!-- !Fdrivers/gpu/drm/drm_bufs.c drm_get_resource_* -->