* Ingo Molnar <mingo@xxxxxxxxxx> wrote: > > As of today I don't see this in linux-next > > > > % git tag --contains 0fc8483b69862 > > next-20180214 > > next-20180215 > > next-20180216 > > > > What happened to this change? > > Hm, so it's a real mystery: I merged it, then removed it 1.5 days later without > reporting anything. According to the Git log timestamp the removal happened late > at night, so maybe it was a tired typo? So just a few seconds after sending this I remembered why I zapped it: it was a Sparse failure reported by the kbuild-test robot. Here's the report: [tip:x86/urgent 14/14] drivers/infiniband/hw/hns/hns_roce_hw_v1.c:1690:22: sparse: incorrect type in argument 1 (different base types) Since you were on Cc: of that report I assumed you'd take care of it. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|