All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mans Rullgard <mans@mansr.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] video: fbdev: fix sys_copyarea
Date: Fri, 30 Jan 2015 07:54:30 +0000	[thread overview]
Message-ID: <54CB38B6.3010202@ti.com> (raw)
In-Reply-To: <1421889589-16362-1-git-send-email-mans@mansr.com>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On 22/01/15 03:19, Mans Rullgard wrote:
> The sys_copyarea() function performs the same operation as
> cfb_copyarea() but using normal memory access instead of I/O
> accessors.  Since the introduction of sys_copyarea(), there
> have been two fixes to cfb_copyarea():
> 
> - 00a9d699 ("framebuffer: fix cfb_copyarea")
> - 5b789da8 ("framebuffer: fix screen corruption when copying")
> 
> This patch incorporates the fixes into sys_copyarea() as well.
> 
> Signed-off-by: Mans Rullgard <mans@mansr.com>
> ---
> Changed in v2:
>  - Fixed wrong first/last calculation in bitcpy_rev()
> ---
>  drivers/video/fbdev/core/syscopyarea.c | 137 ++++++++++++++++-----------------
>  1 file changed, 65 insertions(+), 72 deletions(-)

Thanks, queued for 3.20.

This makes me wonder, though, if the sys and cfb versions could be
somehow combined...

 Tomi



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

WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mans Rullgard <mans@mansr.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	<linux-fbdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] video: fbdev: fix sys_copyarea
Date: Fri, 30 Jan 2015 09:54:30 +0200	[thread overview]
Message-ID: <54CB38B6.3010202@ti.com> (raw)
In-Reply-To: <1421889589-16362-1-git-send-email-mans@mansr.com>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On 22/01/15 03:19, Mans Rullgard wrote:
> The sys_copyarea() function performs the same operation as
> cfb_copyarea() but using normal memory access instead of I/O
> accessors.  Since the introduction of sys_copyarea(), there
> have been two fixes to cfb_copyarea():
> 
> - 00a9d699 ("framebuffer: fix cfb_copyarea")
> - 5b789da8 ("framebuffer: fix screen corruption when copying")
> 
> This patch incorporates the fixes into sys_copyarea() as well.
> 
> Signed-off-by: Mans Rullgard <mans@mansr.com>
> ---
> Changed in v2:
>  - Fixed wrong first/last calculation in bitcpy_rev()
> ---
>  drivers/video/fbdev/core/syscopyarea.c | 137 ++++++++++++++++-----------------
>  1 file changed, 65 insertions(+), 72 deletions(-)

Thanks, queued for 3.20.

This makes me wonder, though, if the sys and cfb versions could be
somehow combined...

 Tomi



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

  reply	other threads:[~2015-01-30  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  1:19 [PATCH v2] video: fbdev: fix sys_copyarea Mans Rullgard
2015-01-30  7:54 ` Tomi Valkeinen [this message]
2015-01-30  7:54   ` Tomi Valkeinen
2015-01-30  8:49   ` Måns Rullgård
2015-01-30  8:49     ` Måns Rullgård

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=54CB38B6.3010202@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mans@mansr.com \
    --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 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.