All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	Daniel Drake <dsd@gentoo.org>,
	linux list <linux-kernel@vger.kernel.org>,
	Jimmy.Jazz@gmx.net
Subject: Re: radeonfb and X800 cards
Date: Fri, 18 May 2007 11:26:52 +1000	[thread overview]
Message-ID: <1179451612.32247.329.camel@localhost.localdomain> (raw)
In-Reply-To: <b637ec0b0705171329i6da89fa8h655976e823aef41e@mail.gmail.com>

On Thu, 2007-05-17 at 22:29 +0200, Fabio Comolli wrote:

> Is there a reason why this patch can't go upstream?

Yes. A change of that magnitude will most certainly introduce
regressions. So we can either:

 - Have it in -mm for monthes trying to iron out all of them (and we'll
miss some). And struggle also since it's hard to track subtle
regressions with very big patches.

 - Have it split in smaller bits, which make it possible to bisect in
case of problem, and thus find/correct problems much faster.

That's my main issue with it at this point. But I'm ok going for route
#1 provided that you guys are willing to help with tracking regressions
down. That also mean I need to do some serious testing on powermacs
since those rely very heavily on a working radeonfb.

Ben.



  reply	other threads:[~2007-05-18  1:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17  1:47 radeonfb and X800 cards Daniel Drake
2007-05-17  1:59 ` Benjamin Herrenschmidt
2007-05-17 12:43   ` Luca
2007-05-17 19:59   ` Luca Tettamanti
2007-05-17 20:29     ` Fabio Comolli
2007-05-18  1:26       ` Benjamin Herrenschmidt [this message]
2007-05-19 20:33         ` Fabio Comolli
2007-05-19 21:16           ` Fabio Comolli
2007-05-18  1:19     ` Benjamin Herrenschmidt
2007-05-20 12:54       ` Jimmy Jazz
2007-05-22 19:31         ` Luca Tettamanti
2007-05-24 21:48           ` Jimmy Jazz

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=1179451612.32247.329.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=Jimmy.Jazz@gmx.net \
    --cc=dsd@gentoo.org \
    --cc=fabio.comolli@gmail.com \
    --cc=kronos.it@gmail.com \
    --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.