From: Al Viro <viro@zeniv.linux.org.uk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v2] nbd: Remove __force casts
Date: Tue, 4 Jun 2024 23:04:31 +0100 [thread overview]
Message-ID: <20240604220431.GU1629371@ZenIV> (raw)
In-Reply-To: <20240604215227.321764-1-bvanassche@acm.org>
On Tue, Jun 04, 2024 at 03:52:27PM -0600, Bart Van Assche wrote:
> From: Christoph Hellwig <hch@lst.de>
>
> Make it again possible for sparse to verify that blk_status_t and Unix
> error codes are used in the proper context by making nbd_send_cmd()
> return a struct instead of an integer.
Not in this version of patch:
> -static int nbd_send_cmd(struct nbd_device *nbd, struct nbd_cmd *cmd, int index)
> +static blk_status_t nbd_send_cmd(struct nbd_device *nbd, struct nbd_cmd *cmd,
> + int index)
include/linux/blk_types.h:93:typedef u8 __bitwise blk_status_t;
next prev parent reply other threads:[~2024-06-04 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 21:52 [PATCH v2] nbd: Remove __force casts Bart Van Assche
2024-06-04 22:04 ` Al Viro [this message]
2024-06-04 22:10 ` 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=20240604220431.GU1629371@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--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