From: Greg KH <gregkh@linuxfoundation.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, pure.logic@nexus-software.ie,
johan@kernel.org, elder@kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] greybus: loopback: remove gb_loopback_async_wait_all()
Date: Sun, 29 Jun 2025 11:47:32 +0200 [thread overview]
Message-ID: <2025062945-prologue-plutonium-870f@gregkh> (raw)
In-Reply-To: <20250628063121.362685-1-pranav.tyagi03@gmail.com>
On Sat, Jun 28, 2025 at 12:01:21PM +0530, Pranav Tyagi wrote:
> Remove redundant gb_loopback_async_wait_all() as connection is disabled
> at the beginning and no further incoming/outgoing requests are possible.
>
> Signed-off-by: Pranav Tyagi <pranav.tyagi03@gmail.com>
> ---
> drivers/staging/greybus/loopback.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c
> index 1f19323b0e1a..9d0d4308ad25 100644
> --- a/drivers/staging/greybus/loopback.c
> +++ b/drivers/staging/greybus/loopback.c
> @@ -1110,13 +1110,6 @@ static void gb_loopback_disconnect(struct gb_bundle *bundle)
> gb_connection_latency_tag_disable(gb->connection);
> debugfs_remove(gb->file);
>
> - /*
> - * FIXME: gb_loopback_async_wait_all() is redundant now, as connection
> - * is disabled at the beginning and so we can't have any more
> - * incoming/outgoing requests.
> - */
> - gb_loopback_async_wait_all(gb);
How was this tested? It might be redundant but I don't think you can
delete this just yet, otherwise we would have done so a long time ago.
And your changelog just says the same thing as this comment, shouldn't
you write something different?
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-29 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 6:31 [PATCH] greybus: loopback: remove gb_loopback_async_wait_all() Pranav Tyagi
2025-06-29 9:47 ` Greg KH [this message]
2025-07-01 9:12 ` Pranav Tyagi
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=2025062945-prologue-plutonium-870f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=pranav.tyagi03@gmail.com \
--cc=pure.logic@nexus-software.ie \
--cc=skhan@linuxfoundation.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