diff options
| author | Juston Li <[email protected]> | 2014-11-18 17:03:51 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2014-11-22 11:02:22 -0800 |
| commit | 962dbfd6144ab04750018b689eddf0857fbc11cb (patch) | |
| tree | 07364c4a22df23aa50b7ec04df50d38110132d63 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 565f3d2fd09a6e9c7615ae369beedabcf0e86b53 (diff) | |
staging: lustre: mdc: use __FMODE_EXEC macro
FMODE_EXEC is type fmode_t but is used in operations
with integers which leads to sparse warnings:
drivers/staging/lustre/lustre/mdc/mdc_lib.c:198:21: warning: restricted fmode_t degrades to integer
drivers/staging/lustre/lustre/mdc/mdc_locks.c:300:49: warning: restricted fmode_t degrades to integer
Fix by using __FMODE_EXEC macro defined in fs.h.
Note the same warnings occurs with other fmode flags
here but they don't have a corresponding int macro.
Changes since v1:
remove ifdefs. FMODE_EXEC and __FMODE_EXEC should
always be defined in fs.h
Signed-off-by: Juston Li <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions