[PATCH v3 06/21] staging: unisys: visorbus: remove putfile_buffer_entry
David Kershner
david.kershner at unisys.com
Fri Sep 2 20:41:30 UTC 2016
From: Jon Frisch <jon.frisch at unisys.com>
This patch removes the unused struct putfile_buffer_entry.
Signed-off-by: Jon Frisch <jon.frisch at unisys.com>
Signed-off-by: David Kershner <david.kershner at unisys.com>
Reported-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
---
drivers/staging/unisys/visorbus/visorchipset.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/staging/unisys/visorbus/visorchipset.c
index 54f90d9..b653a5b 100644
--- a/drivers/staging/unisys/visorbus/visorchipset.c
+++ b/drivers/staging/unisys/visorbus/visorchipset.c
@@ -123,15 +123,6 @@ static struct controlvm_message controlvm_pending_msg;
static bool controlvm_pending_msg_valid;
/*
- * This identifies a data buffer that has been received via a controlvm messages
- * in a remote --> local CONTROLVM_TRANSMIT_FILE conversation.
- */
-struct putfile_buffer_entry {
- struct list_head next; /* putfile_buffer_entry list */
- struct parser_context *parser_ctx; /* points to input data buffer */
-};
-
-/*
* This describes a buffer and its current state of transfer (e.g., how many
* bytes have already been supplied as putfile data, and how many bytes are
* remaining) for a putfile_request.
--
1.9.1
More information about the devel
mailing list