From: Linus Torvalds <torvalds@transmeta.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Ben Collins <bcollins@debian.org>,
James Simmons <jsimmons@infradead.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.69
Date: Wed, 7 May 2003 15:07:34 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0305071504470.3543-100000@home.transmeta.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0305072138510.12013-100000@vervain.sonytel.be>
On Wed, 7 May 2003, Geert Uytterhoeven wrote:
> On Sun, 4 May 2003, Linus Torvalds wrote:
> > Summary of changes from v2.5.68 to v2.5.69
> > ============================================
> >
> > Ben Collins:
> > o [VIDEO]: Revert cfbimgblt.c back to a working state on 64-bit
> > o [VIDEO]: Revert atyfb back to known working clean base
>
> For future changes, could you please run these `reversals' through
> linux-fbdev-devel, instead of silently passing them behind our backs? Thanks!
As mentioned already, this was done by several people, including the
maintainer.
But even if it wasn't, the fact is that new additions that break major
architectures _will_ be reverted. No ifs, buts or maybes about it. If new
code shows itself to be broken, it's going to get reverted, and the sooner
the better. And in this case, the code was not just slightly broken, it
was totally non-working, in ways that made it clear that it had NEVER
worked as intended.
Linus
next prev parent reply other threads:[~2003-05-07 21:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 0:48 Linux 2.5.69 Linus Torvalds
2003-05-05 4:30 ` Florin Iucha
2003-05-05 4:41 ` Linus Torvalds
2003-05-05 6:31 ` Anders Karlsson
2003-05-05 7:08 ` Anders Karlsson
2003-05-05 13:07 ` Florin Iucha
2003-05-05 13:20 ` Florin Iucha
2003-05-05 8:14 ` Benjamin Herrenschmidt
2003-05-05 21:05 ` John Cherry
2003-05-05 21:39 ` Sam Ravnborg
2003-05-05 21:45 ` Arnaldo Carvalho de Melo
2003-05-05 23:22 ` John Cherry
2003-05-06 10:08 ` Paweł Gołaszewski
2003-05-06 12:02 ` [PATCH] include/linux/sunrpc/svc.h compilation error Grzegorz Jaskiewicz
2003-05-06 12:12 ` Grzegorz Jaskiewicz
2003-05-06 12:58 ` Paweł Gołaszewski
2003-05-06 13:39 ` Linux 2.5.69 Roger Luethi
2003-05-06 14:08 ` David S. Miller
2003-05-06 18:24 ` Arnaldo Carvalho de Melo
2003-05-07 2:22 ` Rusty Russell
2003-05-07 19:44 ` Geert Uytterhoeven
2003-05-07 19:35 ` Ben Collins
2003-05-07 22:07 ` Linus Torvalds [this message]
2003-05-05 4:19 Voluspa
[not found] <fa.m5ekdiv.15gu98j@ifi.uio.no>
2003-05-05 13:00 ` walt
[not found] <3EB602ED.3080207@cox.net>
2003-05-05 15:56 ` Linus Torvalds
2003-05-05 16:02 ` William Lee Irwin III
2003-05-05 16:06 ` David van Hoose
2003-05-05 16:16 ` Steven Cole
2003-05-05 18:49 ` Dave Jones
2003-05-05 18:53 ` Linus Torvalds
2003-05-06 7:00 Voluspa
2003-05-06 22:03 Alan Cox
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.44.0305071504470.3543-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=bcollins@debian.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 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).