From: Jens Axboe <[email protected]>
To: kernel test robot <[email protected]>, Ming Lei <[email protected]>
Cc: [email protected],
Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [ammarfaizi2-block:axboe/linux-block/for-6.3/block 148/148] block/blk-merge.c:984:42: sparse: sparse: incorrect type in initializer (different base types)
Date: Thu, 16 Feb 2023 19:52:26 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/16/23 4:47?PM, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
>>> block/blk-merge.c:984:42: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted blk_opf_t const [usertype] ff @@ got unsigned int @@
> block/blk-merge.c:984:42: sparse: expected restricted blk_opf_t const [usertype] ff
> block/blk-merge.c:984:42: sparse: got unsigned int
> block/blk-merge.c:1010:42: sparse: sparse: incorrect type in initializer (different base types) @@ expected restricted blk_opf_t const [usertype] ff @@ got unsigned int @@
> block/blk-merge.c:1010:42: sparse: expected restricted blk_opf_t const [usertype] ff
> block/blk-merge.c:1010:42: sparse: got unsigned int
>>> block/blk-merge.c:763:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@
> block/blk-merge.c:763:24: sparse: expected unsigned int
> block/blk-merge.c:763:24: sparse: got restricted blk_opf_t
> block/blk-merge.c:765:28: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@
> block/blk-merge.c:765:28: sparse: expected unsigned int
> block/blk-merge.c:765:28: sparse: got restricted blk_opf_t
>>> block/blk-merge.c:763:24: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@
> block/blk-merge.c:763:24: sparse: expected unsigned int
> block/blk-merge.c:763:24: sparse: got restricted blk_opf_t
> block/blk-merge.c:765:28: sparse: sparse: incorrect type in return expression (different base types) @@ expected unsigned int @@ got restricted blk_opf_t @@
> block/blk-merge.c:765:28: sparse: expected unsigned int
> block/blk-merge.c:765:28: sparse: got restricted blk_opf_t
I fixed this up, thanks for the report.
--
Jens Axboe
prev parent reply other threads:[~2023-02-17 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:47 [ammarfaizi2-block:axboe/linux-block/for-6.3/block 148/148] block/blk-merge.c:984:42: sparse: sparse: incorrect type in initializer (different base types) kernel test robot
2023-02-17 2:52 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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