linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: drm: Fix typo in drm.tmpl
Date: Mon, 21 Apr 2014 09:26:23 -0700	[thread overview]
Message-ID: <535546AF.6000002@infradead.org> (raw)
In-Reply-To: <1398097026-13800-1-git-send-email-standby24x7@gmail.com>

On 04/21/2014 09:17 AM, Masanari Iida wrote:
> Fix spelling typo in DocBook/drm.tmpl
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>

Applied.  Thanks.

> ---
>  Documentation/DocBook/drm.tmpl | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/DocBook/drm.tmpl b/Documentation/DocBook/drm.tmpl
> index 702c4474..bdb932f 100644
> --- a/Documentation/DocBook/drm.tmpl
> +++ b/Documentation/DocBook/drm.tmpl
> @@ -79,7 +79,7 @@
>    <partintro>
>      <para>
>        This first part of the DRM Developer's Guide documents core DRM code,
> -      helper libraries for writting drivers and generic userspace interfaces
> +      helper libraries for writing drivers and generic userspace interfaces
>        exposed by DRM drivers.
>      </para>
>    </partintro>
> @@ -459,7 +459,7 @@ char *date;</synopsis>
>        providing a solution to every graphics memory-related problems, GEM
>        identified common code between drivers and created a support library to
>        share it. GEM has simpler initialization and execution requirements than
> -      TTM, but has no video RAM management capabitilies and is thus limited to
> +      TTM, but has no video RAM management capabilities and is thus limited to
>        UMA devices.
>      </para>
>      <sect2>
> @@ -889,7 +889,7 @@ int (*prime_fd_to_handle)(struct drm_device *dev,
>  	    vice versa. Drivers must use the kernel dma-buf buffer sharing framework
>  	    to manage the PRIME file descriptors. Similar to the mode setting
>  	    API PRIME is agnostic to the underlying buffer object manager, as
> -	    long as handles are 32bit unsinged integers.
> +	    long as handles are 32bit unsigned integers.
>  	  </para>
>  	  <para>
>  	    While non-GEM drivers must implement the operations themselves, GEM
> @@ -2351,7 +2351,7 @@ void intel_crt_init(struct drm_device *dev)
>        first create properties and then create and associate individual instances
>        of those properties to objects. A property can be instantiated multiple
>        times and associated with different objects. Values are stored in property
> -      instances, and all other property information are stored in the propery
> +      instances, and all other property information are stored in the property
>        and shared between all instances of the property.
>      </para>
>      <para>
> @@ -2692,10 +2692,10 @@ int num_ioctls;</synopsis>
>    <sect1>
>      <title>Legacy Support Code</title>
>      <para>
> -      The section very brievely covers some of the old legacy support code which
> +      The section very briefly covers some of the old legacy support code which
>        is only used by old DRM drivers which have done a so-called shadow-attach
>        to the underlying device instead of registering as a real driver. This
> -      also includes some of the old generic buffer mangement and command
> +      also includes some of the old generic buffer management and command
>        submission code. Do not use any of this in new and modern drivers.
>      </para>
>  
> 


-- 
~Randy

      reply	other threads:[~2014-04-21 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 16:17 [PATCH] doc: drm: Fix typo in drm.tmpl Masanari Iida
2014-04-21 16:26 ` Randy Dunlap [this message]

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=535546AF.6000002@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=standby24x7@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).