#ifndef __PROCFS_FD_H__ #define __PROCFS_FD_H__ #include extern const struct file_operations proc_fd_operations; extern const struct inode_operations proc_fd_inode_operations; extern const struct file_operations proc_fdinfo_operations; extern const struct inode_operations proc_fdinfo_inode_operations; extern int proc_fd_permission(struct inode *inode, int mask); static inline unsigned int proc_fd(struct inode *inode) { return PROC_I(inode)->fd; } #endif /* __PROCFS_FD_H__ */ xt.git' title='net-next.git Git repository'/>
summaryrefslogtreecommitdiff
path: root/drivers/usb/gadget/function/Makefile
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-12-25 14:56:58 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-12-25 14:56:58 -0800
commitd33d5a6c88fcd53fec329a1521010f1bc55fa191 (patch)
treeb95a9598bcf76fd0acc57dff7508cc925db584b6 /drivers/usb/gadget/function/Makefile
parent3ddc76dfc786cc6f87852693227fb0b1f124f807 (diff)
avoid spurious "may be used uninitialized" warning
The timer type simplifications caused a new gcc warning: drivers/base/power/domain.c: In function ‘genpd_runtime_suspend’: drivers/base/power/domain.c:562:14: warning: ‘time_start’ may be used uninitialized in this function [-Wmaybe-uninitialized] elapsed_ns = ktime_to_ns(ktime_sub(ktime_get(), time_start)); despite the actual use of "time_start" not having changed in any way. It appears that simply changing the type of ktime_t from a union to a plain scalar type made gcc check the use. The variable wasn't actually used uninitialized, but gcc apparently failed to notice that the conditional around the use was exactly the same as the conditional around the initialization of that variable. Add an unnecessary initialization just to shut up the compiler. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/usb/gadget/function/Makefile')