Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=102a1a20d2b0a412d4cd4a9f047761f7925405ff
Commit:     102a1a20d2b0a412d4cd4a9f047761f7925405ff
Parent:     b738b990468d2acd5be7fe177fb750448bfa0b37
Author:     Maciej W. Rozycki <[EMAIL PROTECTED]>
AuthorDate: Tue Oct 16 01:29:57 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Tue Oct 16 09:43:23 2007 -0700

    tgafb: remove a redundant non-mono test in mono imageblit
    
    There is a test in tgafb_mono_imageblit() for a colour image with a 
fall-back
    to cfb_imageblit().  The test is not necessary as the only caller, which is
    tgafb_imageblit(), checks it too and only invokes this function for 
monochrome
    images.  It looks like a left-over from before some changes to
    tgafb_imageblit().
    
    Signed-off-by: Maciej W. Rozycki <[EMAIL PROTECTED]>
    Cc: Antonino Daplas <[EMAIL PROTECTED]>
    Cc: Jay Estabrook <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
---
 drivers/video/tgafb.c |    9 ---------
 1 files changed, 0 insertions(+), 9 deletions(-)

diff --git a/drivers/video/tgafb.c b/drivers/video/tgafb.c
index 5539f4d..680642c 100644
--- a/drivers/video/tgafb.c
+++ b/drivers/video/tgafb.c
@@ -637,15 +637,6 @@ tgafb_mono_imageblit(struct fb_info *info, const struct 
fb_image *image)
 
        is8bpp = info->var.bits_per_pixel == 8;
 
-       /* For copies that aren't pixel expansion, there's little we
-          can do better than the generic code.  */
-       /* ??? There is a DMA write mode; I wonder if that could be
-          made to pull the data from the image buffer...  */
-       if (image->depth > 1) {
-               cfb_imageblit(info, image);
-               return;
-       }
-
        dx = image->dx;
        dy = image->dy;
        width = image->width;
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to