Docbook: correction of drm_device to drm_driver
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH 3/5 Documentation: log_buf_len uses [KMG] suffix
From: Randy Dunlap <[email protected]>
Update the "log_buf_len" description to use [KMG] syntax for the buffer size.
Signed-off-by Randy Dunlap <[email protected]>
--- Documentation/kernel-parameters.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
Documentation/kernel-parameters.txt +3 -4
@@ -1271,10 +1271,9 @@ bytes respectively. Such letter suffixes 6 (KERN_INFO) informational 7 (KERN_DEBUG) debug-level messages - log_buf_len=n Sets the size of the printk ring buffer, in bytes. - Format: { n | nk | nM } - n must be a power of two. The default size - is set in the kernel config file. + log_buf_len=n[KMG] Sets the size of the printk ring buffer, + in bytes. n must be a power of two. The default + size is set in the kernel config file. logo.nologo [FB] Disables display of the built-in Linux logo. This may be used to provide more screen space for
PATCH 4/5 Docbook: add fs/eventfd.c and fix typos in it
In reply to a message not in the archiveFrom: Randy Dunlap <[email protected]>
Add fs/eventfd.c to filesystems docbook.
Make typo corrections in fs/eventfd.c.
Signed-off-by Randy Dunlap <[email protected]>
Cc Davide Libenzi <[email protected]>
--- Documentation/DocBook/filesystems.tmpl | 5 +++++ fs/eventfd.c | 12 ++++++------ 2 files changed, 11 insertions(+), 6 deletions(-)
Documentation/DocBook/filesystems.tmpl +5 -0
@@ -82,6 +82,11 @@ </sect1> </chapter> + <chapter id="fs_events"> + <title>Events based on file descriptors</title> +!Efs/eventfd.c + </chapter> + <chapter id="sysfs"> <title>The Filesystem for Exporting Kernel Objects</title> !Efs/sysfs/file.c
fs/eventfd.c +6 -6
@@ -99,7 +99,7 @@ EXPORT_SYMBOL_GPL(eventfd_ctx_get);* @ctx: [in] Pointer to eventfd context. * * The eventfd context reference must have been previously acquired either -* with eventfd_ctx_get() or eventfd_ctx_fdget()). +* with eventfd_ctx_get() or eventfd_ctx_fdget(). */ void eventfd_ctx_put (struct eventfd_ctx *ctx) {
@@ -146,9 +146,9 @@ static void eventfd_ctx_do_read(struct e* eventfd_ctx_remove_wait_queue - Read the current counter and removes wait queue. * @ctx: [in] Pointer to eventfd context. * @wait: [in] Wait queue to be removed. -* @cnt: [out] Pointer to the 64bit conter value. +* @cnt: [out] Pointer to the 64-bit counter value. * -* Returns zero if successful, or the following error codes: +* Returns %0 if successful, or the following error codes: * * -EAGAIN : The operation would have blocked. *
@@ -175,11 +175,11 @@ EXPORT_SYMBOL_GPL(eventfd_ctx_remove_wai* eventfd_ctx_read - Reads the eventfd counter or wait if it is zero. * @ctx: [in] Pointer to eventfd context. * @no_wait: [in] Different from zero if the operation should not block. -* @cnt: [out] Pointer to the 64bit conter value. +* @cnt: [out] Pointer to the 64-bit counter value. * -* Returns zero if successful, or the following error codes: +* Returns %0 if successful, or the following error codes: * -* -EAGAIN : The operation would have blocked but @no_wait was nonzero. +* -EAGAIN : The operation would have blocked but @no_wait was non-zero. * -ERESTARTSYS : A signal interrupted the wait operation. * * If @no_wait is zero, the function might sleep until the eventfd internal
PATCH 5/5 Docbook: correction of drm_device to drm_driver
In reply to a message not in the archiveFrom: Xiao Jiang <[email protected]>
A few wrong usages of drm_device, which should be drm_driver.
Signed-off-by Xiao Jiang <[email protected]>
Signed-off-by Randy Dunlap <[email protected]>
Acked-by Jesse Barnes <[email protected]>
--- Documentation/DocBook/drm.tmpl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/DocBook/drm.tmpl +3 -3
@@ -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 = {