From: Pavel Begunkov <[email protected]>
To: Jiapeng Chong <[email protected]>, [email protected]
Cc: [email protected], [email protected],
Abaci Robot <[email protected]>
Subject: Re: [PATCH] io_uring/notif: Remove the unused function io_notif_complete()
Date: Mon, 5 Sep 2022 12:41:18 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/5/22 03:04, Jiapeng Chong wrote:
> The function io_notif_complete() is defined in the notif.c file, but not
> called elsewhere, so delete this unused function.
Yep, forgot to kill it, LGTM
Reviewed-by: Pavel Begunkov <[email protected]>
> io_uring/notif.c:24:20: warning: unused function 'io_notif_complete' [-Wunused-function].
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2047
> Reported-by: Abaci Robot <[email protected]>
> Signed-off-by: Jiapeng Chong <[email protected]>
> ---
> io_uring/notif.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/io_uring/notif.c b/io_uring/notif.c
> index 96f076b175e0..1a7abd7e5ca5 100644
> --- a/io_uring/notif.c
> +++ b/io_uring/notif.c
> @@ -21,14 +21,6 @@ static void __io_notif_complete_tw(struct io_kiocb *notif, bool *locked)
> io_req_task_complete(notif, locked);
> }
>
> -static inline void io_notif_complete(struct io_kiocb *notif)
> - __must_hold(¬if->ctx->uring_lock)
> -{
> - bool locked = true;
> -
> - __io_notif_complete_tw(notif, &locked);
> -}
> -
> static void io_uring_tx_zerocopy_callback(struct sk_buff *skb,
> struct ubuf_info *uarg,
> bool success)
--
Pavel Begunkov
next prev parent reply other threads:[~2022-09-05 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 2:04 [PATCH] io_uring/notif: Remove the unused function io_notif_complete() Jiapeng Chong
2022-09-05 11:41 ` Pavel Begunkov [this message]
2022-09-05 17:42 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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