Re: [Linux-fbdev-devel] drivers/video/imsttfb.c: setclkMHz: clk_p is always 0

Adrian Bunk wrote:
> The Coverity checker noticed that in the function setclkMHz in 
> drivers/video/imsttfb.c, the variable clk_p is never assigned a value 
> other than 0.
> 
> Could someone understanding this code decide whether this is a real bug 
> or whether clk_p can be replaced by 0?
> 

It does look like to be an oversight.  The same is present in Xorg code
too.

Tony

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- drivers/video/imsttfb.c: setclkMHz: clk_p is always 0
  - From: Adrian Bunk <[email protected]>

Prev by Date: Re: [PATCH] non-linear frame buffer read/write access
Next by Date: [PATCH] Drop vmlinux dependency from "make install"
Previous by thread: drivers/video/imsttfb.c: setclkMHz: clk_p is always 0
Next by thread: drivers/acpi/scan.c: inconsequent NULL handling
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]