From: Pranav Tyagi <pranav.tyagi03@gmail.com>
To: greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: pure.logic@nexus-software.ie, johan@kernel.org, elder@kernel.org,
gregkh@linuxfoundation.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
Pranav Tyagi <pranav.tyagi03@gmail.com>
Subject: [PATCH] greybus: loopback: remove gb_loopback_async_wait_all()
Date: Sat, 28 Jun 2025 12:01:21 +0530 [thread overview]
Message-ID: <20250628063121.362685-1-pranav.tyagi03@gmail.com> (raw)
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);
-
spin_lock_irqsave(&gb_dev.lock, flags);
gb_dev.count--;
spin_unlock_irqrestore(&gb_dev.lock, flags);
--
2.49.0
next reply other threads:[~2025-06-28 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 6:31 Pranav Tyagi [this message]
2025-06-29 9:47 ` [PATCH] greybus: loopback: remove gb_loopback_async_wait_all() Greg KH
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=20250628063121.362685-1-pranav.tyagi03@gmail.com \
--to=pranav.tyagi03@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.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=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