From: Ming Lei <ming.lei@redhat.com>
To: Yoav Cohen <yoav@nvidia.com>
Cc: linux-block@vger.kernel.org, csander@purestorage.com,
jholzman@nvidia.com, omril@nvidia.com
Subject: Re: [PATCH v2 1/2] ublk: make ublk_ctrl_stop_dev return void
Date: Tue, 6 Jan 2026 22:14:36 +0800 [thread overview]
Message-ID: <aV0YzBOjurnbip6K@fedora> (raw)
In-Reply-To: <20260104084839.30065-2-yoav@nvidia.com>
On Sun, Jan 04, 2026 at 10:48:38AM +0200, Yoav Cohen wrote:
> This function always returns 0, so there is no need to return a value.
>
> Signed-off-by: Yoav Cohen <yoav@nvidia.com>
> ---
> drivers/block/ublk_drv.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/block/ublk_drv.c b/drivers/block/ublk_drv.c
> index 837fedb02e0d..2d5602ef05cc 100644
> --- a/drivers/block/ublk_drv.c
> +++ b/drivers/block/ublk_drv.c
> @@ -3304,10 +3304,9 @@ static inline void ublk_ctrl_cmd_dump(struct io_uring_cmd *cmd)
> header->data[0], header->addr, header->len);
> }
>
> -static int ublk_ctrl_stop_dev(struct ublk_device *ub)
> +static void ublk_ctrl_stop_dev(struct ublk_device *ub)
> {
> ublk_stop_dev(ub);
> - return 0;
> }
>
> static int ublk_ctrl_get_dev_info(struct ublk_device *ub,
> @@ -3780,7 +3779,8 @@ static int ublk_ctrl_uring_cmd(struct io_uring_cmd *cmd,
> ret = ublk_ctrl_start_dev(ub, header);
> break;
> case UBLK_CMD_STOP_DEV:
> - ret = ublk_ctrl_stop_dev(ub);
> + ublk_ctrl_stop_dev(ub);
> + ret = 0;
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks
Ming
next prev parent reply other threads:[~2026-01-06 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 8:48 [PATCH v2 0/2] ublk: introduce UBLK_CMD_TRY_STOP_DEV Yoav Cohen
2026-01-04 8:48 ` [PATCH v2 1/2] ublk: make ublk_ctrl_stop_dev return void Yoav Cohen
2026-01-06 14:14 ` Ming Lei [this message]
2026-01-04 8:48 ` [PATCH v2 2/2] ublk: add UBLK_CMD_TRY_STOP_DEV command Yoav Cohen
2026-01-06 14:28 ` Ming Lei
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=aV0YzBOjurnbip6K@fedora \
--to=ming.lei@redhat.com \
--cc=csander@purestorage.com \
--cc=jholzman@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=omril@nvidia.com \
--cc=yoav@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.