[<prev] [next>] [day] [month] [year] [list]
Message-ID: <12982613152740@xenotime.net>
Date: Sun, 20 Feb 2011 20:08:35 -0800
From: Randy Dunlap <rdunlap@...otime.net>
To: linux-kernel@...r.kernel.org
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: [PATCH 5/5] Docbook: correction of drm_device to drm_driver
From: Xiao Jiang <jgq516@...il.com>
A few wrong usages of drm_device, which should be drm_driver.
Signed-off-by: Xiao Jiang <jgq516@...il.com>
Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
Acked-by: Jesse Barnes <jbarnes@...tuousgeek.org>
---
Documentation/DocBook/drm.tmpl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- lnx-2638-rc3.orig/Documentation/DocBook/drm.tmpl
+++ lnx-2638-rc3/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 = {
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists