From: Andrew Morton <akpm@osdl.org>
To: mpm@selenic.com, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
benh@kernel.crashing.org
Subject: Re: Radeon framebuffer weirdness in -mm2
Date: Thu, 20 Jan 2005 20:07:11 -0800 [thread overview]
Message-ID: <20050120200711.4313dbcc.akpm@osdl.org> (raw)
In-Reply-To: <20050120200530.4d5871f9.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> Next suspects would be:
>
> +cleanup-vc-array-access.patch
> +remove-console_macrosh.patch
> +merge-vt_struct-into-vc_data.patch
>
>
Make that:
+cleanup-vc-array-access.patch
+remove-console_macrosh.patch
+merge-vt_struct-into-vc_data.patch
+vgacon-fixes-to-help-font-restauration-in-x11.patch
and the fbdev updates, maybe:
+radeonfb-set-accelerator-id.patch
+vesafb-change-return-error-id.patch
+intelfb-workaround-for-830m.patch
+fbcon-save-blank-state-last.patch
+backlight-fix-compile-error-if-config_fb-is-unset.patch
+matroxfb-fb_matrox_g-kconfig-changes.patch
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-21 4:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:21 Radeon framebuffer weirdness in -mm2 Matt Mackall
2005-01-20 23:39 ` Andrew Morton
2005-01-20 23:48 ` Matt Mackall
2005-01-21 0:01 ` Andrew Morton
2005-01-21 3:57 ` Matt Mackall
2005-01-21 4:05 ` Andrew Morton
2005-01-21 4:07 ` Andrew Morton [this message]
2005-01-21 6:09 ` Matt Mackall
2005-01-21 12:33 ` Roman Zippel
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-22 0:52 ` Matt Mackall
2005-01-24 4:00 ` Benjamin Herrenschmidt
2005-01-21 16:36 ` Antonino A. Daplas
2005-01-21 0:03 ` Benjamin Herrenschmidt
2005-01-21 0:24 ` James Simmons
2005-01-21 0:03 ` 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=20050120200711.4313dbcc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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).