From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] block: Remove unused blk_op_is_blocked()
Date: Thu, 6 Feb 2025 18:25:47 +0100 [thread overview]
Message-ID: <b46b9348-0f28-4714-8b39-13cf2e62a649@linaro.org> (raw)
In-Reply-To: <20250206165331.379033-1-kwolf@redhat.com>
On 6/2/25 17:53, Kevin Wolf wrote:
> Commit fc4e394b28 removed the last caller of blk_op_is_blocked(). Remove
> the now unused function.
fatal: ambiguous argument 'fc4e394b28': unknown revision or path not in
the working tree.
Is there a patch on the list?
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> include/system/block-backend-global-state.h | 1 -
> block/block-backend.c | 12 ------------
> 2 files changed, 13 deletions(-)
>
> diff --git a/include/system/block-backend-global-state.h b/include/system/block-backend-global-state.h
> index 9cc9b008ec..35b5e8380b 100644
> --- a/include/system/block-backend-global-state.h
> +++ b/include/system/block-backend-global-state.h
> @@ -86,7 +86,6 @@ bool blk_supports_write_perm(BlockBackend *blk);
> bool blk_is_sg(BlockBackend *blk);
> void blk_set_enable_write_cache(BlockBackend *blk, bool wce);
> int blk_get_flags(BlockBackend *blk);
> -bool blk_op_is_blocked(BlockBackend *blk, BlockOpType op, Error **errp);
> int blk_set_aio_context(BlockBackend *blk, AioContext *new_context,
> Error **errp);
> void blk_add_aio_context_notifier(BlockBackend *blk,
> diff --git a/block/block-backend.c b/block/block-backend.c
> index 9288f7e1c6..a402db13f2 100644
> --- a/block/block-backend.c
> +++ b/block/block-backend.c
> @@ -2357,18 +2357,6 @@ void *blk_blockalign(BlockBackend *blk, size_t size)
> return qemu_blockalign(blk ? blk_bs(blk) : NULL, size);
> }
>
> -bool blk_op_is_blocked(BlockBackend *blk, BlockOpType op, Error **errp)
> -{
> - BlockDriverState *bs = blk_bs(blk);
> - GLOBAL_STATE_CODE();
> - GRAPH_RDLOCK_GUARD_MAINLOOP();
> -
> - if (!bs) {
> - return false;
> - }
> -
> - return bdrv_op_is_blocked(bs, op, errp);
> -}
>
> /**
> * Return BB's current AioContext. Note that this context may change
next prev parent reply other threads:[~2025-02-06 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 16:53 [PATCH] block: Remove unused blk_op_is_blocked() Kevin Wolf
2025-02-06 17:25 ` Philippe Mathieu-Daudé [this message]
2025-02-06 20:44 ` Kevin Wolf
2025-02-10 11:44 ` Philippe Mathieu-Daudé
2025-02-06 18:11 ` Stefan Hajnoczi
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=b46b9348-0f28-4714-8b39-13cf2e62a649@linaro.org \
--to=philmd@linaro.org \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).