linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Eric Engestrom <eric@engestrom.ch>, linux-kernel@vger.kernel.org
Cc: Bernie Thompson <bernie@plugable.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-fbdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 24/41] Documentation: fb: fix spelling mistakes
Date: Tue, 10 May 2016 09:06:20 +0000	[thread overview]
Message-ID: <5731A48C.4070004@ti.com> (raw)
In-Reply-To: <1461543878-3639-25-git-send-email-eric@engestrom.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1950 bytes --]

On 25/04/16 03:24, Eric Engestrom wrote:
> Signed-off-by: Eric Engestrom <eric@engestrom.ch>
> ---
>  Documentation/fb/udlfb.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/fb/udlfb.txt b/Documentation/fb/udlfb.txt
> index 57d2f29..c985cb6 100644
> --- a/Documentation/fb/udlfb.txt
> +++ b/Documentation/fb/udlfb.txt
> @@ -9,7 +9,7 @@ pairing that with a hardware framebuffer (16MB) on the other end of the
>  USB wire.  That hardware framebuffer is able to drive the VGA, DVI, or HDMI
>  monitor with no CPU involvement until a pixel has to change.
>  
> -The CPU or other local resource does all the rendering; optinally compares the
> +The CPU or other local resource does all the rendering; optionally compares the
>  result with a local shadow of the remote hardware framebuffer to identify
>  the minimal set of pixels that have changed; and compresses and sends those
>  pixels line-by-line via USB bulk transfers.
> @@ -66,10 +66,10 @@ means that from a hardware and fbdev software perspective, everything is good.
>  At that point, a /dev/fb? interface will be present for user-mode applications
>  to open and begin writing to the framebuffer of the DisplayLink device using
>  standard fbdev calls.  Note that if mmap() is used, by default the user mode
> -application must send down damage notifcations to trigger repaints of the
> +application must send down damage notifications to trigger repaints of the
>  changed regions.  Alternatively, udlfb can be recompiled with experimental
>  defio support enabled, to support a page-fault based detection mechanism
> -that can work without explicit notifcation.
> +that can work without explicit notification.
>  
>  The most common client of udlfb is xf86-video-displaylink or a modified
>  xf86-video-fbdev X server. These servers have no real DisplayLink specific
> 

Thanks, queued for 4.7.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-05-10  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1461543878-3639-1-git-send-email-eric@engestrom.ch>
2016-04-25  0:24 ` [PATCH 24/41] Documentation: fb: fix spelling mistakes Eric Engestrom
2016-05-10  9:06   ` Tomi Valkeinen [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=5731A48C.4070004@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=bernie@plugable.com \
    --cc=corbet@lwn.net \
    --cc=eric@engestrom.ch \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.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).