From: <ajoshi@kernel.crashing.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] radeonfb 0.1.9 against 2.4.21pre2 (fwd)
Date: Wed, 16 Jul 2003 13:28:04 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10307161326280.22306-100000@gate.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307161514050.12905@freak.distro.conectiva>
Haha, ok this is geting ridiculous, it seems the childish games are still
being played. I don't have time for this, Ben you can find a maintainer
for the driver or do it yourself.
On Wed, 16 Jul 2003, Marcelo Tosatti wrote:
>
> On Wed, 16 Jul 2003 ajoshi@kernel.crashing.org wrote:
>
> >
> >
> > Many of these have already been addressed in 0.1.9,
>
> He is talking about 0.1.9. The issues he complained about are present in
> 0.1.9. I havent read one line of code, but I know him enough to know he's
> has no reason to lie or come up with non-existant bugs.
>
> Please resend me a patch when you really have addressed the issues
> Benjamin pointed out (0.1.10 or whatever).
>
> For now I'll stick to 0.1.8 + his fixes.
>
> > though I added the usage of the native clock, assertion for it, the dvi
> > blanking, and the nolcd passthrough. For things like the updated PM
> > code, a patch would be helpful.
>
next prev parent reply other threads:[~2003-07-16 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 13:05 [PATCH] radeonfb 0.1.9 against 2.4.21pre2 (fwd) Marcelo Tosatti
2003-07-16 14:18 ` Benjamin Herrenschmidt
2003-07-16 18:10 ` ajoshi
2003-07-16 18:17 ` Marcelo Tosatti
2003-07-16 18:28 ` ajoshi [this message]
2003-07-16 18:31 ` Marcelo Tosatti
2003-07-16 20:18 ` Benjamin Herrenschmidt
2003-07-16 20:17 ` Benjamin Herrenschmidt
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=Pine.LNX.4.10.10307161326280.22306-100000@gate.crashing.org \
--to=ajoshi@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).