From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH] null_blk: Fix two sparse warnings
Date: Sat, 11 May 2024 11:03:58 -0600 [thread overview]
Message-ID: <171544703866.418778.16613935289747164338.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240510201816.24921-1-bvanassche@acm.org>
On Fri, 10 May 2024 13:18:16 -0700, Bart Van Assche wrote:
> Fix the following sparse warnings:
>
> drivers/block/null_blk/main.c:1243:35: warning: incorrect type in return expression (different base types)
> drivers/block/null_blk/main.c:1243:35: expected int
> drivers/block/null_blk/main.c:1243:35: got restricted blk_status_t
> drivers/block/null_blk/main.c:1291:30: warning: incorrect type in return expression (different base types)
> drivers/block/null_blk/main.c:1291:30: expected restricted blk_status_t
> drivers/block/null_blk/main.c:1291:30: got int
>
> [...]
Applied, thanks!
[1/1] null_blk: Fix two sparse warnings
commit: e655d93e55b9ef7508b59d2d42a58549a37fd4aa
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-05-11 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:18 [PATCH] null_blk: Fix two sparse warnings Bart Van Assche
2024-05-11 17:03 ` 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 \
--in-reply-to=171544703866.418778.16613935289747164338.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).