Hi Jason, It seems that kbuild has put my patch on to the wrong git tree for test. I have checked on for-next tree according to the reproduce steps, it didn't report such warnings. Could I just ignore this kbuild report? On 2018/2/26 20:46, kbuild test robot wrote: > Hi Yixian, > > Thank you for the patch! Perhaps something to improve: > > [auto build test WARNING on linus/master] > [also build test WARNING on v4.16-rc3 next-20180226] > [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/Yixian-Liu/Support-rq-and-cq-record-doorbell/20180226-184438 > reproduce: > # apt-get install sparse > make ARCH=x86_64 allmodconfig > make C=1 CF=-D__CHECK_ENDIAN__ > > > sparse warnings: (new ones prefixed by >>) > > drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1223:9: left side has type unsigned int > drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1223:9: right side has type restricted __le32 > drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1225:9: sparse: invalid assignment: &= > drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1225:9: left side has type unsigned int -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
