Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <dc0dbf3d-d524-7edc-6fbf-0067c75c3d03@acm.org>
Date:   Sat, 6 Aug 2022 08:21:56 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in
 argument 5 (different base types)
Content-Language: en-US
To:     kernel test robot <lkp@intel.com>
Cc:     kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
        Jens Axboe <axboe@kernel.dk>
References: <202208061258.jAwlaAXe-lkp@intel.com>
From:   Bart Van Assche <bvanassche@acm.org>
In-Reply-To: <202208061258.jAwlaAXe-lkp@intel.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.