sdhci: 'scratch' may be used uninitialized
authorSteven Noonan <steven@uplinklabs.net>
Wed, 1 Oct 2008 08:50:25 +0000 (01:50 -0700)
committerPierre Ossman <drzeus@drzeus.cx>
Sun, 12 Oct 2008 09:04:36 +0000 (11:04 +0200)
commit7244b85bd17313d7d300ee93ec7bfbca1f4ccf3d
tree96ba4ef056e3c351ac9a01e4deca359aa1e10c82
parent57105737f6a0b39305a85ac176cc9fd4a236d8c2
sdhci: 'scratch' may be used uninitialized

The variable 'scratch' is always initialized before it's used. The
conditional which is responsible for initialization of 'scratch' will
always evaluate 'true' when the first loop iteration occurs, and thus,
it's properly initialized. GCC doesn't see this, of course, so using
the uninitialized_var() macro seems to work for silencing this case.

Signed-off-by: Steven Noonan <steven@uplinklabs.net>
Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
drivers/mmc/host/sdhci.c