arm, fbdev, omap2, LLVMLinux: Remove nested function from omapfb

Replace the use of nested functions where a normal function will suffice.

Nested functions are not liked by upstream kernel developers in general. Their
use breaks the use of clang as a compiler, and doesn't make the code any
better.

This code now works for both gcc and clang.

Signed-off-by: Behan Webster <behanw@converseincode.com>
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Cc: Arnd Bergmann <arnd@arndb.de>
Reviewed-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
This commit is contained in:
Behan Webster 2014-09-26 18:10:53 -07:00 committed by Tomi Valkeinen
parent 032e57f01b
commit c8b8888f09

View File

@ -273,16 +273,16 @@ static struct omapfb_colormode omapfb_colormodes[] = {
}, },
}; };
static bool cmp_component(struct fb_bitfield *f1, struct fb_bitfield *f2)
{
return f1->length == f2->length &&
f1->offset == f2->offset &&
f1->msb_right == f2->msb_right;
}
static bool cmp_var_to_colormode(struct fb_var_screeninfo *var, static bool cmp_var_to_colormode(struct fb_var_screeninfo *var,
struct omapfb_colormode *color) struct omapfb_colormode *color)
{ {
bool cmp_component(struct fb_bitfield *f1, struct fb_bitfield *f2)
{
return f1->length == f2->length &&
f1->offset == f2->offset &&
f1->msb_right == f2->msb_right;
}
if (var->bits_per_pixel == 0 || if (var->bits_per_pixel == 0 ||
var->red.length == 0 || var->red.length == 0 ||
var->blue.length == 0 || var->blue.length == 0 ||