linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Waiting for patches in main line
Date: Tue, 13 Dec 2005 17:30:59 +0100	[thread overview]
Message-ID: <439EF743.7000400@t-online.de> (raw)
In-Reply-To: <439E22B3.3080200@gmail.com>


>>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
>>    
>>
>
>  
>
Thanks for the quick reaction. All the patches cyblafb needs to compile 
and work are
included in git3 now.

A test showed that minor errors that were corrected by the patches I 
received from
Antonino remain in git3 --- bitstream font 16x30 is broken a bit, as 
well as rotation 2.
But these cases are not as broken as without the patches ;-)

I have no time left today and will sort out things tomorrow.

cu,
 Knut




-------------------------------------------------------
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

      reply	other threads:[~2005-12-13 16:52 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
2005-12-13 16:30         ` Knut Petersen [this message]

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=439EF743.7000400@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=adaplas@gmail.com \
    --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 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).