From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Eger <eger@theboonies.us>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.3-rc3 radeonfb: Problems with new (and old) driver
Date: Tue, 17 Feb 2004 11:04:05 +1100 [thread overview]
Message-ID: <1076976245.3648.114.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0402161546460.30742@home.osdl.org>
> Oh, there is no hurry with this. In fact, I'd rather take it slow than try
> to make any big changes to something that _largely_ works but has problems
> in some special cases.
>
> In fact, I'd be happiest if the first step would be to just rename the
> interface and change the argument infrastructure, but actually keep all
> the behaviour "obviously the same". Bugs and all, if it comes to that. So
> I'd rather take several small steps (and let people use it for a while in
> between) than try to do everything. And yes, 2.6.3 is not even a target.
That's fine with me.
Ben.
next prev parent reply other threads:[~2004-02-17 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.50L0.0402160411260.2959-100000@rosencrantz.theboonies.us>
2004-02-16 4:01 ` 2.6.3-rc3 radeonfb: Problems with new (and old) driver Benjamin Herrenschmidt
2004-02-16 17:56 ` Linus Torvalds
2004-02-16 21:50 ` Benjamin Herrenschmidt
2004-02-16 22:13 ` Linus Torvalds
2004-02-16 22:18 ` Benjamin Herrenschmidt
2004-02-16 22:30 ` Linus Torvalds
2004-02-16 22:57 ` Benjamin Herrenschmidt
2004-02-16 23:09 ` Linus Torvalds
2004-02-16 23:31 ` Benjamin Herrenschmidt
2004-02-16 23:49 ` Linus Torvalds
2004-02-17 0:04 ` Benjamin Herrenschmidt [this message]
2004-02-15 6:16 [PATCH] Remove debug cruft from via-pmu.c driver Benjamin Herrenschmidt
2004-02-15 18:02 ` 2.6.3-rc3 radeonfb: Problems with new (and old) driver Mike Houston
2004-02-15 21:01 ` Petr Vandrovec
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=1076976245.3648.114.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=eger@theboonies.us \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox