From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Bart Van Assche <bvanassche@acm.org>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [kbuild-all] Re: drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types)
Date: Tue, 9 Aug 2022 18:23:21 +0800 [thread overview]
Message-ID: <bd67a6dd-4d43-28f6-e2bb-a283f581a7a9@intel.com> (raw)
In-Reply-To: <dc0dbf3d-d524-7edc-6fbf-0067c75c3d03@acm.org>
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
next prev parent reply other threads:[~2022-08-09 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 4:44 drivers/md/raid10.c:2647:60: sparse: sparse: incorrect type in argument 5 (different base types) kernel test robot
2022-08-06 15:21 ` Bart Van Assche
2022-08-06 15:21 ` Bart Van Assche
2022-08-09 10:23 ` Chen, Rong A [this message]
2022-08-09 13:22 ` Bart Van Assche
2022-08-09 13:22 ` [kbuild-all] " Bart Van Assche
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd67a6dd-4d43-28f6-e2bb-a283f581a7a9@intel.com \
--to=rong.a.chen@intel.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.