From: Roel Kluin <12o3l-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
To: Stephane Marchesin
<marchesin-YynmYXH4S6491FlJP1ih0VAUjnlXr6A1@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] free nvs->pass_rec on error in nouveau_shader_pass2(), nouveau_shader_2.c
Date: Wed, 30 Jan 2008 12:34:49 +0100 [thread overview]
Message-ID: <47A060D9.9030800@tiscali.nl> (raw)
In-Reply-To: <6a89f9d50801291636j32cb1e39j79c4a921b3c3a9d2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Stephane Marchesin wrote:
> Hi Roel,
>
> All your patches correct valid flaws. However, as you might have
> noticed, the old DRI code doesn't see much development at the moment.
> The reason is that we've decided to jump in the gallium3D wagon before
> it was even finished. So you have to know that this piece of code is
> currently not maintained, and that you'd have to finish it by yourself
> mostly.
>
> I can of course push your patches if you feel like actually working on
> finishing this old-scheme DRI driver. Just tell me.
>
> Stephane
Thanks for your information. I'll focus on gallium3D development instead.
However, since my patches correct valid flaws, maybe it's best to push
these patches. Is it a lot of work? If not, please do.
Chances are that someone in the future copy/pastes code, and with that
these flaws, or that at a later time it is decided that the original
driver was the better.
Roel Kluin
prev parent reply other threads:[~2008-01-30 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 23:56 [PATCH] free nvs->pass_rec on error in nouveau_shader_pass2(), nouveau_shader_2.c Roel Kluin
[not found] ` <479FBD2B.3020309-IWqWACnzNjzz+pZb47iToQ@public.gmane.org>
2008-01-30 0:36 ` Stephane Marchesin
[not found] ` <6a89f9d50801291636j32cb1e39j79c4a921b3c3a9d2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-30 11:34 ` Roel Kluin [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=47A060D9.9030800@tiscali.nl \
--to=12o3l-iwqwacnznjzz+pzb47itoq@public.gmane.org \
--cc=marchesin-YynmYXH4S6491FlJP1ih0VAUjnlXr6A1@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.