From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org
Cc: Xiao Jiang <jgq516@gmail.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: [PATCH 5/5] Docbook: correction of drm_device to drm_driver
Date: Sun, 20 Feb 2011 20:08:35 -0800 [thread overview]
Message-ID: <12982613152740@xenotime.net> (raw)
In-Reply-To: <1298261315935@xenotime.net>
From: Xiao Jiang <jgq516@gmail.com>
A few wrong usages of drm_device, which should be drm_driver.
Signed-off-by: Xiao Jiang <jgq516@gmail.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Acked-by: Jesse Barnes <jbarnes@virtuousgeek.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 = {
--
next parent reply other threads:[~2011-02-21 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1298261315935@xenotime.net>
2011-02-21 4:08 ` Randy Dunlap [this message]
2011-02-21 4:08 ` [PATCH 3/5] Documentation: log_buf_len uses [KMG] suffix Randy Dunlap
2011-02-21 4:08 ` [PATCH 4/5] Docbook: add fs/eventfd.c and fix typos in it Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12982613152740@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.