From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fbdev cursor part 1.
Date: Tue, 17 Feb 2004 10:35:27 +1100 [thread overview]
Message-ID: <1076974526.1046.105.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402162221001.21833-100000@phoenix.infradead.org>
On Tue, 2004-02-17 at 09:26, James Simmons wrote:
> Hi!
>
> I broke up the cursor patch. This patch creates a seperate cursor
> image drawing region and regular drawing region. It does not break any
> drivers to my knowledge. I posted it anyways for people to test it. The
> patch is against 2.6.3-rc3. Please try.
Andrew, that one seem to work fine for me, been hammered for some time
in the fbdev tree. It should go to -mm for a while imho so we get more
broader testing, and eventually in 2.6.4
Ben.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fbdev cursor part 1.
Date: Tue, 17 Feb 2004 10:35:27 +1100 [thread overview]
Message-ID: <1076974526.1046.105.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402162221001.21833-100000@phoenix.infradead.org>
On Tue, 2004-02-17 at 09:26, James Simmons wrote:
> Hi!
>
> I broke up the cursor patch. This patch creates a seperate cursor
> image drawing region and regular drawing region. It does not break any
> drivers to my knowledge. I posted it anyways for people to test it. The
> patch is against 2.6.3-rc3. Please try.
Andrew, that one seem to work fine for me, been hammered for some time
in the fbdev tree. It should go to -mm for a while imho so we get more
broader testing, and eventually in 2.6.4
Ben.
next prev parent reply other threads:[~2004-02-16 23:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 22:26 fbdev cursor part 1 James Simmons
2004-02-16 22:26 ` James Simmons
2004-02-16 23:35 ` Benjamin Herrenschmidt [this message]
2004-02-16 23:35 ` Benjamin Herrenschmidt
2004-02-16 23:41 ` James Simmons
2004-02-16 23:41 ` James Simmons
2004-02-22 21:06 ` Alexander Kern
2004-02-22 22:37 ` James Simmons
2004-02-23 0:35 ` Benjamin Herrenschmidt
2004-02-23 10:57 ` Geert Uytterhoeven
2004-02-23 10:59 ` Benjamin Herrenschmidt
2004-02-23 12:44 ` Geert Uytterhoeven
2004-02-23 13:21 ` Ville Syrjälä
2004-02-23 13:51 ` Geert Uytterhoeven
2004-02-24 0:55 ` Ville Syrjälä
2004-02-23 22:53 ` Benjamin Herrenschmidt
2004-03-05 9:03 ` Alexander Kern
2004-03-10 17:49 ` James Simmons
2004-03-11 5:05 ` Benjamin Herrenschmidt
2004-03-11 17:05 ` James Simmons
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=1076974526.1046.105.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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.