Content-Type: multipart/mixed; boundary="===============0698562964642636197==" MIME-Version: 1.0 From: kbuild test robot To: kbuild-all@lists.01.org Subject: Re: [PATCH] vfs: Handle file systems without ->parse_params better Date: Sun, 22 Dec 2019 02:36:11 +0800 Message-ID: <201912220244.6ohMQ4WK%lkp@intel.com> In-Reply-To: <20191212213604.19525-1-labbott@redhat.com> List-Id: --===============0698562964642636197== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Laura, I love your patch! Perhaps something to improve: [auto build test WARNING on vfs/for-next] [cannot apply to dhowells-fs/fscache-next linus/master v5.5-rc2 next-201912= 20] [if your patch is applied to the wrong git tree, please drop us a note to h= elp 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/37406= 982] url: https://github.com/0day-ci/linux/commits/Laura-Abbott/vfs-Handle-fi= le-systems-without-parse_params-better/20191216-053622 base: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-ne= xt reproduce: # apt-get install sparse # sparse version: v0.6.1-129-g341daf20-dirty make ARCH=3Dx86_64 allmodconfig make C=3D1 CF=3D'-fdiagnostic-prefix -D__CHECK_ENDIAN__' If you fix the issue, kindly add following tag Reported-by: kbuild test robot sparse warnings: (new ones prefixed by >>) >> fs/fs_context.c:119:39: sparse: sparse: symbol 'generic_fs_parameters' w= as not declared. Should it be static? Please review and possibly fold the followup patch. --- 0-DAY kernel test infrastructure Open Source Technology Cen= ter https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corpor= ation --===============0698562964642636197==--