summary refs log tree commit diff
path: root/Documentation
diff options
context:
space:
mode:
authorXiao Jiang <jgq516@gmail.com>2011-02-14 17:58:23 +0800
committerDave Airlie <airlied@redhat.com>2011-02-15 09:01:29 +1000
commitbd91572e77013aad242e2d2d565bd730c043f8b8 (patch)
tree98ca606124a25c7759a967cb54146ef741c10868 /Documentation
parent265aa6c8d8822c9074a2174e8c9f31a37fa02e50 (diff)
downloadlinux-bd91572e77013aad242e2d2d565bd730c043f8b8.tar.gz
drm: fix wrong usages of drm_device in DRM Developer's Guide
A few wrong usages of drm_device, which should be drm_driver.

Signed-off-by: Xiao Jiang <jgq516@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/DocBook/drm.tmpl6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
index 2861055afd7a..c27915893974 100644
--- a/Documentation/DocBook/drm.tmpl
+++ b/Documentation/DocBook/drm.tmpl
@@ -73,8 +73,8 @@
       services.
     </para>
     <para>
-      The core of every DRM driver is struct drm_device.  Drivers
-      will typically statically initialize a drm_device structure,
+      The core of every DRM driver is struct drm_driver.  Drivers
+      will typically statically initialize a drm_driver structure,
       then pass it to drm_init() at load time.
     </para>
 
@@ -84,7 +84,7 @@
     <title>Driver initialization</title>
     <para>
       Before calling the DRM initialization routines, the driver must
-      first create and fill out a struct drm_device structure.
+      first create and fill out a struct drm_driver structure.
     </para>
     <programlisting>
       static struct drm_driver driver = {