From: Bart Van Assche <bvanassche@acm.org>
To: "Chen, Rong A" <rong.a.chen@intel.com>,
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 06:22:23 -0700 [thread overview]
Message-ID: <8f6abe4e-17a0-7f20-1383-a044188e0bc8@acm.org> (raw)
In-Reply-To: <bd67a6dd-4d43-28f6-e2bb-a283f581a7a9@intel.com>
On 8/9/22 03:23, Chen, Rong A wrote:
> 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 @@
Thanks, I can reproduce this warning. I will send a fix.
Best regards,
Bart.
prev parent reply other threads:[~2022-08-09 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 4:44 kernel test robot
2022-08-06 15:21 ` Bart Van Assche
2022-08-09 10:23 ` [kbuild-all] " Chen, Rong A
2022-08-09 13:22 ` Bart Van Assche [this message]
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=8f6abe4e-17a0-7f20-1383-a044188e0bc8@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rong.a.chen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®