summaryrefslogtreecommitdiffstats
path: root/arch/s390/tools
diff options
context:
space:
mode:
authorSteffen Maier <maier@linux.vnet.ibm.com>2017-10-17 18:40:51 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2017-11-16 15:06:19 +0100
commit5c13db9b5df2dc97b0d4ce9d442bbcd80b5194b7 (patch)
tree310d939f219e983b930e4b37ada740127cea3d20 /arch/s390/tools
parent75492a51568b943e903e1d7de10a962fbc001ba6 (diff)
downloadlinux-5c13db9b5df2dc97b0d4ce9d442bbcd80b5194b7.tar.bz2
zfcp: purely mechanical update using timer API, plus blank lines
erp_memwait only occurs in seldom memory pressure situations. The typical case never uses the associated timer and thus also does not need to initialize the timer. Also, we don't want to re-initialize the timer each time we re-use an erp_action in zfcp_erp_setup_act() [see also v4.14-rc7 commit ab31fd0ce65e ("scsi: zfcp: fix erp_action use-before-initialize in REC action trace") for erp_action life cycle]. Hence, retain the lazy inintialization of zfcp_erp_action.timer in zfcp_erp_strategy_memwait(). Add an empty line after declarations in zfcp_erp_timeout_handler() and zfcp_fsf_request_timeout_handler() even though it was also missing before the timer conversion. Fix checkpatch warning: WARNING: function definition argument 'struct timer_list *' should also have an identifier name +extern void zfcp_erp_timeout_handler(struct timer_list *); Depends-on: v4.14-rc3 commit 686fef928bba ("timer: Prepare to change timer callback argument type") Signed-off-by: Steffen Maier <maier@linux.vnet.ibm.com> Reviewed-by: Jens Remus <jremus@linux.vnet.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/tools')
0 files changed, 0 insertions, 0 deletions