From: Kronos <kronos@kronoz.cjb.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org
Subject: Re: [PATCH] cg*: New framebuffer_alloc API and class_dev changes
Date: Wed, 17 Sep 2003 18:37:34 +0200 [thread overview]
Message-ID: <20030917163734.GA8032@dreamland.darkstar.lan> (raw)
In-Reply-To: <20030916182146.6c848c59.davem@redhat.com>
Il Tue, Sep 16, 2003 at 06:21:46PM -0700, David S. Miller ha scritto:
> On Tue, 16 Sep 2003 15:46:03 +0200
> Kronos <kronos@kronoz.cjb.net> wrote:
>
> > Btw, how do the patches look?
>
> They look fine, just push them into James tree.
As Russell King pointed out there was a flaw in that API. I reworked it
a bit. I've patched sparc drivers:
drivers/video/bw2.c
drivers/video/cg14.c
drivers/video/cg3.c
drivers/video/cg6.c
drivers/video/ffb.c
drivers/video/leo.c
drivers/video/p9100.c
drivers/video/tcx.c
Patches are almost identical to the ones I sent to you, but I removed
the release_* callback. If you want to take a look I've just pushed the
changeset:
bk://mesa3d@bkbits.net/fbdev-2.5
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
"Fare l'amore con dieci donne e` fantastico, soprattutto perche` ti
presentano un sacco di amiche." -- Fabio Di Iorio
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-09-17 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 19:42 [PATCH] cg*: New framebuffer_alloc API and class_dev changes Kronos
2003-09-15 23:27 ` David S. Miller
2003-09-16 13:46 ` Kronos
2003-09-17 1:21 ` David S. Miller
2003-09-17 16:37 ` Kronos [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=20030917163734.GA8032@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=davem@redhat.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).