From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Morton <akpm@osdl.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, adaplas@pol.net
Subject: Re: [Linux-fbdev-devel] fbdev broken in current bk for PPC
Date: Tue, 21 Sep 2004 03:38:00 +0800 [thread overview]
Message-ID: <200409210338.00863.adaplas@hotpop.com> (raw)
In-Reply-To: <20040920085214.0abe33a0.akpm@osdl.org>
On Monday 20 September 2004 23:52, Andrew Morton wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> > Andrew, Any reason why this patch isn't upstream ? The recent changes
> > to fbdev in 2.6.9-* are a regression and we need this patch to get bac
> > the video=ofonly feature.
>
> Well I have a whole bunch of fbcon/fbdev patches here, but at some point
> one needs to plug the flow so we can get 2.6.9 out the door. And nobody
> told me (until now) that we had a problem.
>
> Tony, which of the below shold be merged into 2.6.9?
>
> fbdev-fix-userland-compile-breakage.patch
> fbcon-fix-fbcons-setup-routine.patch
> fbdev-arrange-driver-order-in-makefile.patch
These 3 need to go to mainline.
> fbdev-fix-logo-drawing-failure-for-vga16fb.patch
> fbcon-fix-setup-boot-options-of-fbcon.patch
These 2 need not go immediately as no one will probably notice what they
fixed.
> radeonfb-fix-warnings-about-uninitialized-variables.patch
I haven't seen this.
> fbdev-remove-unnecessary-banshee_wait_idle-from-tdfxfb.patch
> fbdev-initialize-i810fb-after-agpgart.patch
> fbdev-pass-struct-device-to-class_simple_device_add.patch
> fbdev-add-tile-blitting-support.patch
> fbdev-fix-scrolling-corruption.patch
> fbdev-remove-i810fb-explicit-agp-initialization-hack.patch
These can wait.
Tony
next prev parent reply other threads:[~2004-09-20 19:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 2:23 fbdev broken in current bk for PPC Benjamin Herrenschmidt
2004-09-10 2:23 ` Benjamin Herrenschmidt
2004-09-10 5:28 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10 5:28 ` Antonino A. Daplas
2004-09-10 6:00 ` Benjamin Herrenschmidt
2004-09-10 6:00 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-09-10 8:07 ` Geert Uytterhoeven
2004-09-10 8:07 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-09-10 8:35 ` Antonino A. Daplas
2004-09-10 8:35 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-11 1:04 ` Antonino A. Daplas
2004-09-11 1:04 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-09-10 8:35 ` Antonino A. Daplas
2004-09-10 8:48 ` Anton Blanchard
2004-09-10 17:52 ` David Eger
2004-09-10 21:27 ` Antonino A. Daplas
2004-09-10 21:27 ` Antonino A. Daplas
2004-09-10 23:40 ` David Eger
2004-09-11 7:19 ` Geert Uytterhoeven
2004-09-11 7:19 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-09-10 21:04 ` Antonino A. Daplas
2004-09-11 1:00 ` Benjamin Herrenschmidt
2004-09-13 1:52 ` Joseph Fannin
2004-09-20 9:27 ` Benjamin Herrenschmidt
2004-09-20 9:27 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2004-09-20 15:52 ` Andrew Morton
2004-09-20 19:38 ` Antonino A. Daplas [this message]
2004-09-20 19:59 ` Antonino A. Daplas
2004-09-20 19:59 ` Antonino A. Daplas
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=200409210338.00863.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 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.