diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-07-27 20:03:31 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-07-27 20:03:31 -0700 |
commit | 194dc870a5890e855ecffb30f3b80ba7c88f96d6 (patch) | |
tree | 776c4bf61bac8d6fe722926317ba9d757c6e054a /crypto/ansi_cprng.c | |
parent | 124a3d88fa20e1869fc229d7d8c740cc81944264 (diff) | |
download | linux-stable-194dc870a5890e855ecffb30f3b80ba7c88f96d6.tar.gz linux-stable-194dc870a5890e855ecffb30f3b80ba7c88f96d6.tar.bz2 linux-stable-194dc870a5890e855ecffb30f3b80ba7c88f96d6.zip |
Add braces to avoid "ambiguous ‘else’" compiler warnings
Some of our "for_each_xyz()" macro constructs make gcc unhappy about
lack of braces around if-statements inside or outside the loop, because
the loop construct itself has a "if-then-else" statement inside of it.
The resulting warnings look something like this:
drivers/gpu/drm/i915/i915_debugfs.c: In function ‘i915_dump_lrc’:
drivers/gpu/drm/i915/i915_debugfs.c:2103:6: warning: suggest explicit braces to avoid ambiguous ‘else’ [-Wparentheses]
if (ctx != dev_priv->kernel_context)
^
even if the code itself is fine.
Since the warning is fairly easy to avoid by adding a braces around the
if-statement near the for_each_xyz() construct, do so, rather than
disabling the otherwise potentially useful warning.
(The if-then-else statements used in the "for_each_xyz()" constructs are
designed to be inherently safe even with no braces, but in this case
it's quite understandable that gcc isn't really able to tell that).
This finally leaves the standard "allmodconfig" build with just a
handful of remaining warnings, so new and valid warnings hopefully will
stand out.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto/ansi_cprng.c')
0 files changed, 0 insertions, 0 deletions