From: Jeremy Dean Clifton <deaner92@yahoo.com>
To: Viresh Kumar <vireshk@kernel.org>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: outreachy@lists.linux.dev,
Jeremy Dean Clifton <deaner92@yahoo.com>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] staging: greybus: Remove unused header declaration to_fw_mgmt_connection
Date: Wed, 14 Oct 2026 17:42:48 +0000 [thread overview]
Message-ID: <20261014174248.97561-1-deaner92@yahoo.com> (raw)
In-Reply-To: <20261014174248.97561-1-deaner92.ref@yahoo.com>
Previous commit removing a function definition did not remove the
function prototype.
commit 3228900f80c2 ("staging: greybus: Remove unused function
'to_fw_mgmt_connection'")
Function header declaration needs to be removed after definition
removal.
There is no definition of this function nor is there any place where it
is called.
Signed-off-by: Jeremy Dean Clifton <deaner92@yahoo.com>
---
v2: Fix grammar and spelling in commit message.
drivers/staging/greybus/firmware.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/greybus/firmware.h b/drivers/staging/greybus/firmware.h
index 5d2564462ffc..04a67d2d5b8f 100644
--- a/drivers/staging/greybus/firmware.h
+++ b/drivers/staging/greybus/firmware.h
@@ -22,7 +22,6 @@
/* Firmware Management Protocol specific functions */
int fw_mgmt_init(void);
void fw_mgmt_exit(void);
-struct gb_connection *to_fw_mgmt_connection(struct device *dev);
int gb_fw_mgmt_request_handler(struct gb_operation *op);
int gb_fw_mgmt_connection_init(struct gb_connection *connection);
void gb_fw_mgmt_connection_exit(struct gb_connection *connection);
--
2.43.0
next parent reply other threads:[~2026-10-14 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261014174248.97561-1-deaner92.ref@yahoo.com>
2026-10-14 17:42 ` Jeremy Dean Clifton [this message]
2026-10-15 1:46 ` Julia Lawall
2026-10-15 2:10 ` Jeremy Clifton
2026-10-15 2:22 ` Julia Lawall
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=20261014174248.97561-1-deaner92@yahoo.com \
--to=deaner92@yahoo.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=vireshk@kernel.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
all inboxes | Powered by JetHome®