summaryrefslogtreecommitdiffstats
path: root/crypto/Kconfig
diff options
context:
space:
mode:
authorArnd Bergmann2016-01-26 14:44:50 +0100
committerHerbert Xu2016-01-27 13:36:26 +0100
commitbfb2892018ca302d8d659232f5f18f56b4b2b782 (patch)
tree8f9e5d0d314a148f2e80eea81542a1896df628b2 /crypto/Kconfig
parentlibceph: Remove unnecessary ivsize variables (diff)
downloadkernel-qcow2-linux-bfb2892018ca302d8d659232f5f18f56b4b2b782.tar.gz
kernel-qcow2-linux-bfb2892018ca302d8d659232f5f18f56b4b2b782.tar.xz
kernel-qcow2-linux-bfb2892018ca302d8d659232f5f18f56b4b2b782.zip
crypto: sunxi - don't print confusing data
gcc correctly warns that the printk output contains a variable that it thinks is not initialized in some cases: drivers/crypto/sunxi-ss/sun4i-ss-cipher.c: In function 'sun4i_ss_cipher_poll': drivers/crypto/sunxi-ss/sun4i-ss-cipher.c:254:76: warning: 'todo' may be used uninitialized in this function [-Wmaybe-uninitialized] drivers/crypto/sunxi-ss/sun4i-ss-cipher.c:144:15: note: 'todo' was declared here A closer look at the function reveals that the variable is always initialized at this point (ileft is guaranteed to be positive at the start), but its contents are not well-defined: Depending on some other variables, it might be either a count in words or bytes, and it could refer to either input or output. The easiest solution apparently is to remove the confusing output and let the reader figure out the state from the other variables. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/Kconfig')
0 files changed, 0 insertions, 0 deletions