The patch titled
tgafb: remove a redundant non-mono test in mono imageblit
has been removed from the -mm tree. Its filename was
tgafb-remove-a-redundant-non-mono-test-in-mono-imageblit.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: tgafb: remove a redundant non-mono test in mono imageblit
From: "Maciej W. Rozycki" <macro@xxxxxxxxxxxxxx>
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 <macro@xxxxxxxxxxxxxx>
Cc: Antonino Daplas <adaplas@xxxxxxx>
Cc: Jay Estabrook <Jay.Estabrook@xxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/video/tgafb.c | 9 ---------
1 file changed, 9 deletions(-)
diff -puN drivers/video/tgafb.c~tgafb-remove-a-redundant-non-mono-test-in-mono-imageblit drivers/video/tgafb.c
--- a/drivers/video/tgafb.c~tgafb-remove-a-redundant-non-mono-test-in-mono-imageblit
+++ a/drivers/video/tgafb.c
@@ -637,15 +637,6 @@ tgafb_mono_imageblit(struct fb_info *inf
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;
_
Patches currently in -mm which might be from macro@xxxxxxxxxxxxxx are
origin.patch
include-linux-typesh-in-if_fddih.patch
avoid-negative-and-full-width-shifts-in-radix-treec.patch
lk201-remove-obsolete-driver.patch
kernel-printkc-concerns-about-the-console-handover.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
