From: Adrian Bunk <bunk@stusta.de>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: drivers/video/imsttfb.c: setclkMHz: clk_p is always 0
Date: Fri, 6 Jan 2006 17:25:54 +0100 [thread overview]
Message-ID: <20060106162554.GJ12131@stusta.de> (raw)
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?
TIA
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2006-01-06 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 16:25 Adrian Bunk [this message]
2006-01-07 1:34 ` [Linux-fbdev-devel] drivers/video/imsttfb.c: setclkMHz: clk_p is always 0 Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 19:53 Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060106162554.GJ12131@stusta.de \
--to=bunk@stusta.de \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox