Validating monitor timings (was: Re: [PATCH] video: fbdev: amifb.c: Cleaning up variable that is never used)

From: Geert Uytterhoeven
Date: Sat Jul 05 2014 - 10:06:46 EST


On Sat, Jul 5, 2014 at 4:04 PM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote:
> On Sat, Jul 5, 2014 at 2:13 PM, Rickard Strandqvist
> <rickard_strandqvist@xxxxxxxxxxxxxxxxxx> wrote:
>> From: Rickard Strandqvist <rickard.strandqvist@xxxxxxxxxxxxxx>
>>
>> Variable ar assigned a value that is never used.
>> I have also removed all the code that thereby serves no purpose.
>>
>> This was found using a static code analysis program called cppcheck
>>
>> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@xxxxxxxxxxxxxxxxxx>
>
> Acked-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
>
>> --- a/drivers/video/fbdev/amifb.c
>> +++ b/drivers/video/fbdev/amifb.c
>> @@ -1124,7 +1124,6 @@ static int ami_decode_var(struct fb_var_screeninfo *var, struct amifb_par *par,
>> {
>> u_short clk_shift, line_shift;
>> u_long maxfetchstop, fstrt, fsize, fconst, xres_n, yres_n;
>> - u_int htotal, vtotal;
>
> These became unused by commit 3161986224a3faa8ccca3e665b7404d81e7ee3cf
> Author: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
> Date: Wed Dec 13 00:35:54 2006 -0800
>
> [PATCH] fbdev: remove references to non-existent fbmon_valid_timings()
>
> Remove references to non-existent fbmon_valid_timings()

These days there's fb_validate_mode(), but very few drivers call that.
Or perhaps this should be handled by the fbdev core instead?
But there's potential for regressions here, as monspecs may not be set at all
with some drivers, and the default assumptions in fb_validate_mode() may not
be valid.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/