Hi Harshad, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on tip/perf/core] [cannot apply to ext4/dev linus/master v5.5-rc3 next-20191220] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Harshad-Shirwadkar/ext4-update-docs-for-fast-commit-feature/20191225-200339 base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ceb9e77324fa661b1001a0ae66f061b5fcb4e4e6 reproduce: # apt-get install sparse # sparse version: v0.6.1-129-g341daf20-dirty make ARCH=x86_64 allmodconfig make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' If you fix the issue, kindly add following tag Reported-by: kbuild test robot <lkp@xxxxxxxxx> sparse warnings: (new ones prefixed by >>) fs/ext4/ext4_jbd2.c:611:5: sparse: sparse: symbol '__ext4_fc_track_range' was not declared. Should it be static? >> fs/ext4/ext4_jbd2.c:825:6: sparse: sparse: symbol 'submit_fc_bh' was not declared. Should it be static? >> fs/ext4/ext4_jbd2.c:1156:5: sparse: sparse: symbol 'ext4_fc_perform_hard_commit' was not declared. Should it be static? fs/ext4/ext4_jbd2.c:500:12: sparse: sparse: context imbalance in '__ext4_dentry_update' - unexpected unlock >> fs/ext4/ext4_jbd2.c:923:20: sparse: sparse: context imbalance in 'wait_all_inode_data' - unexpected unlock Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx Intel Corporation
