From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, Vasily Averin <vasily.averin@linux.dev>
Cc: kernel@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk-mq: use force attribute for blk_status_t casts
Date: Sat, 14 May 2022 15:24:20 -0600 [thread overview]
Message-ID: <165256346055.208046.4012136969482600787.b4-ty@kernel.dk> (raw)
In-Reply-To: <e3251f58-fd47-9b94-387b-ab641a773dd7@openvz.org>
On Sat, 14 May 2022 13:03:54 +0300, Vasily Averin wrote:
> Fixes sparse warnings:
> block/blk-mq.c:1163:36: sparse:
> warning: cast from restricted blk_status_t
> block/blk-mq.c:1251:17: sparse:
> warning: cast to restricted blk_status_t
>
>
> [...]
Applied, thanks!
[1/1] blk-mq: use force attribute for blk_status_t casts
commit: cb9e061e974f8a3a8f2b8c89d93f34ffa7cacafb
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2022-05-14 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 10:03 [PATCH] blk-mq: use force attribute for blk_status_t casts Vasily Averin
2022-05-14 21:24 ` Jens Axboe [this message]
2022-05-16 6:53 ` Christoph Hellwig
2022-05-18 12:45 ` [PATCH v2] blk-mq: fix incorrect " Vasily Averin
2022-05-18 20:35 ` Chaitanya Kulkarni
2022-05-19 7:53 ` Christoph Hellwig
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=165256346055.208046.4012136969482600787.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=kernel@openvz.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vasily.averin@linux.dev \
/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 NNTP newsgroup(s).