From: Ali Gholami Rudi <ali@rudi.ir>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Cc: Krzysztof Helt <krzysztof.h1@wp.pl>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Philippe De Muyter <phdm@macqel.be>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Righi <righi.andrea@gmail.com>
Subject: [PATCH 0/2] fbdev: add fillrect and copyarea ioctls
Date: Mon, 13 Jul 2009 19:47:09 +0430 [thread overview]
Message-ID: <20090713151709.GA1297@lilem.mirepesht> (raw)
Hi,
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.
Ali Gholami Rudi (2):
fbdev: add FBIOFILLRECT ioctl
fbdev: add FBIOCOPYAREA ioctl
drivers/video/fbmem.c | 50 +++++++++++++++++++++++++++++++++++++++++++++++++
include/linux/fb.h | 2 +
2 files changed, 52 insertions(+), 0 deletions(-)
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
next reply other threads:[~2009-07-13 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 15:17 Ali Gholami Rudi [this message]
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
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=20090713151709.GA1297@lilem.mirepesht \
--to=ali@rudi.ir \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--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