Messages in this thread | | | Date | Sat, 6 Aug 2022 08:21:56 -0700 | Subject | Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types) | From | Bart Van Assche <> |
| |
On 8/5/22 21:44, kernel test robot wrote: > drivers/md/raid10.c:1139:30: sparse: sparse: incorrect type in initializer (different base types) @@ expected int const op @@ got restricted blk_opf_t enum req_op @@ > drivers/md/raid10.c:1139:30: sparse: expected int const op > drivers/md/raid10.c:1139:30: sparse: got restricted blk_opf_t enum req_op > drivers/md/raid10.c:1140:52: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long const do_sync @@ got restricted blk_opf_t @@ > drivers/md/raid10.c:1140:52: sparse: expected unsigned long const do_sync > drivers/md/raid10.c:1140:52: sparse: got restricted blk_opf_t
I can't reproduce this with Linus' master branch. It seems like the kernel test robot picked a commit somewhere halfway my patch series?
Bart.
| |