On Tue, Feb 20, 2018 at 11:17:03AM +1100, NeilBrown wrote: > On Mon, Feb 19 2018, kbuild test robot wrote: > > > Hi NeilBrown, > > > > Thank you for the patch! Perhaps something to improve: > > > > [auto build test WARNING on nfs/linux-next] > > [also build test WARNING on v4.16-rc2 next-20180219] > > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > > > url: https://github.com/0day-ci/linux/commits/NeilBrown/Remove-generic-rpc-credentials-and-associated-changed-V3/20180219-190836 > > base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next > > reproduce: > > # apt-get install sparse > > make ARCH=x86_64 allmodconfig > > make C=1 CF=-D__CHECK_ENDIAN__ > > > > > > sparse warnings: (new ones prefixed by >>) > > > >>> fs/nfs/flexfilelayout/flexfilelayout.c:517:40: sparse: incorrect type in initializer (different address spaces) @@ expected struct cred const @@ got cred const @@ > > fs/nfs/flexfilelayout/flexfilelayout.c:517:40: expected struct cred const > > fs/nfs/flexfilelayout/flexfilelayout.c:517:40: got struct cred const Documentation Kbuild Kconfig Makefile certs drivers firmware fs include samples scripts sound tools cred > > Hi Mr Robot :-) > It looks like you have some strange wild-card expansion happening here. > I think the above should be > > fs/nfs/flexfilelayout/flexfilelayout.c:517:40: got struct cred const * cred thanks for pointing this out, we will fix it. > > Even after correcting the that, I cannot see what the different address > spaces are that might be a problem. > Does anyone have any ideas? > > Thanks, > NeilBrown > _______________________________________________ > kbuild-all mailing list > kbuild-all@xxxxxxxxxxxx > https://lists.01.org/mailman/listinfo/kbuild-all -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
