kbuild test robot <lkp@xxxxxxxxx> writes: > sparse warnings: (new ones prefixed by >>) > >>> fs/nls/nls_default.c:118:20: sparse: incorrect type in assignment >>> (different base types) @@ expected unsigned short [unsigned] [short] >>> [usertype] <noident> @@ got unsigned] [short] [usertype] <noident> @@ > fs/nls/nls_default.c:118:20: expected unsigned short [unsigned] [short] [usertype] <noident> > fs/nls/nls_default.c:118:20: got restricted __le16 [usertype] <noident> > fs/nls/nls_default.c:121:20: sparse: incorrect type in assignment > (different base types) @@ expected unsigned short [unsigned] [short] > [usertype] <noident> @@ got unsigned] [short] [usertype] <noident> @@ > fs/nls/nls_default.c:121:20: expected unsigned short [unsigned] [short] [usertype] <noident> > fs/nls/nls_default.c:121:20: got restricted __be16 [usertype] <noident> [snip.] This is not caused by my patch, but it is identified because I am moving code around. I don't plan to fix it in my patch set at this moment. -- Gabriel Krisman Bertazi
