From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Knut_Petersen@t-online.de, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Waiting for patches in main line
Date: Tue, 13 Dec 2005 09:24:03 +0800 [thread overview]
Message-ID: <439E22B3.3080200@gmail.com> (raw)
In-Reply-To: <20051212170854.7bb9f75c.akpm@osdl.org>
Andrew Morton wrote:
> "Antonino A. Daplas" <adaplas@gmail.com> wrote:
>>> fbdev-fix-incorrect-unaligned-access-in-little-endian-machines.patch
>> This one is a real bug fix.
>
> OK, this one causes me some grief, because it changes things which aren't
> in Linus's tree yet.
>
> <looks>
>
> If I merge
> fbdev-shift-pixel-value-before-entering-loop-in-cfbimageblit.patch as well,
> all is good.
Yes, that's a safe patch to include.
>
> So to confirm, after a compile test I'll send the following along to Linus
> for 2.6.15:
>
> fbcon-add-ability-to-save-restore-graphics-state.patch
> fbdev-pan-display-fixes.patch
> fbcon-avoid-illegal-display-panning.patch
> fbdev-fixing-switch-to-kd_text-enhanced-version.patch
> fbdev-shift-pixel-value-before-entering-loop-in-cfbimageblit.patch
> fbdev-fix-incorrect-unaligned-access-in-little-endian-machines.patch
Yes.
>
> There's also
>
> fbcon-fix-complement_mask-with-512-character-map.patch
>
> which I have yet to test. I guess we can hold off on that?
>
Yes, the worst that can happen is a bad gpm cursor.
Tony
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-13 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 18:06 Waiting for patches in main line Knut Petersen
2005-12-12 20:15 ` Andrew Morton
2005-12-13 0:28 ` Antonino A. Daplas
2005-12-13 1:08 ` Andrew Morton
2005-12-13 1:24 ` Antonino A. Daplas [this message]
2005-12-13 16:30 ` Knut Petersen
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=439E22B3.3080200@gmail.com \
--to=adaplas@gmail.com \
--cc=Knut_Petersen@t-online.de \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.