Re: [kbuild-all] Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types)

[Chen, Rong A]

On 8/6/2022 11:21 PM, Bart Van Assche wrote:
> 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.

Hi Bart,

Only the warning prefixed by '>>' is related to this commit 4ce4c73f662b:

>> drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in 
argument 5 (different base types) @@     expected restricted blk_opf_t 
[usertype] opf @@     got int rw @@

and I can reproduce it in my system.

Best Regards,
Rong Chen