From: Ali Gholami Rudi <ali@rudi.ir>
To: Greg KH <gregkh@suse.de>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Righi <righi.andrea@gmail.com>,
Krzysztof Helt <krzysztof.h1@wp.pl>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Philippe De Muyter <phdm@macqel.be>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] fbdev: add fillrect and copyarea ioctls
Date: Tue, 14 Jul 2009 00:38:04 +0430 [thread overview]
Message-ID: <20090713200804.GB1280@lilem.mirepesht> (raw)
In-Reply-To: <20090713163530.GA22251@suse.de>
Greg KH <gregkh@suse.de> wrote:
> On Mon, Jul 13, 2009 at 07:47:09PM +0430, Ali Gholami Rudi wrote:
> > Is there any reason for not adding these ioctls to fbdev? I searched
> > the net and couldn't any. Anyway, these patches simply implement those
> > ioctls.
>
> Have you also added the needed 32 vs. 64 bit handlers for these ioctls?
I guess Arnd's patch will do.
By the way, it should check for overflows, too? I mean should I change
this:
> + if (copy->dx + copy->width > info->var.xres ||
> + copy->sx + copy->width > info->var.xres ||
> + copy->dy + copy->height > info->var.yres ||
> + copy->sy + copy->height > info->var.yres) {
#define ISSUMLESSTHAN(a, b, s) (((a) <= (s)) && ((b) <= (s)) && \
((a) + (b) <= (s)))
if (!ISSUMLESSTHAN(copy->dx, copy->width, info->var.xres) || ...
Ali
prev parent reply other threads:[~2009-07-13 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 15:17 [PATCH 0/2] fbdev: add fillrect and copyarea ioctls Ali Gholami Rudi
2009-07-13 15:18 ` [PATCH 1/2] fbdev: add FBIOFILLRECT ioctl Ali Gholami Rudi
2009-07-13 15:20 ` [PATCH 2/2] fbdev: add FBIOCOPYAREA ioctl Ali Gholami Rudi
2009-07-13 15:40 ` [PATCH 0/2] fbdev: add fillrect and copyarea ioctls Arjan van de Ven
2009-07-13 16:25 ` Ali Gholami Rudi
2009-07-14 0:46 ` Dave Airlie
2009-07-14 3:43 ` Ali Gholami Rudi
2009-07-14 3:56 ` Dave Airlie
2009-07-14 9:47 ` Stelios Xanthakis
2009-07-13 16:35 ` Greg KH
2009-07-13 18:53 ` Arnd Bergmann
2009-07-13 19:52 ` Ali Gholami Rudi
2009-07-13 20:08 ` Ali Gholami Rudi [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=20090713200804.GB1280@lilem.mirepesht \
--to=ali@rudi.ir \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=krzysztof.h1@wp.pl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=righi.andrea@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