[PATCH 1/7] staging: unisys: visorbus: Remove unused enum members

[David Kershner]

Visorchipset used to parse CONTROLVM messages with a variety of string
information. All but the name string have been removed, but the code
to handle this information remained. This patch removes the other values
and handlers.

Signed-off-by: Bryan Thompson <bryan.thomp...@unisys.com>
Signed-off-by: David Kershner <david.kersh...@unisys.com>
---
 drivers/staging/unisys/visorbus/visorchipset.c | 17 +----------------
 1 file changed, 1 insertion(+), 16 deletions(-)

diff --git a/drivers/staging/unisys/visorbus/visorchipset.c 
b/drivers/staging/unisys/visorbus/visorchipset.c
index 501eb9e..f883bc3 100644
--- a/drivers/staging/unisys/visorbus/visorchipset.c
+++ b/drivers/staging/unisys/visorbus/visorchipset.c
@@ -364,10 +364,7 @@ parser_id_get(struct parser_context *ctx)
  */
 
 enum PARSER_WHICH_STRING {
-       PARSERSTRING_INITIATOR,
-       PARSERSTRING_TARGET,
-       PARSERSTRING_CONNECTION,
-       PARSERSTRING_NAME, /* TODO: only PARSERSTRING_NAME is used ? */
+       PARSERSTRING_NAME
 };
 
 static void
@@ -381,18 +378,6 @@ parser_param_start(struct parser_context *ctx,
 
        phdr = (struct spar_controlvm_parameters_header *)(ctx->data);
        switch (which_string) {
-       case PARSERSTRING_INITIATOR:
-               ctx->curr = ctx->data + phdr->initiator_offset;
-               ctx->bytes_remaining = phdr->initiator_length;
-               break;
-       case PARSERSTRING_TARGET:
-               ctx->curr = ctx->data + phdr->target_offset;
-               ctx->bytes_remaining = phdr->target_length;
-               break;
-       case PARSERSTRING_CONNECTION:
-               ctx->curr = ctx->data + phdr->connection_offset;
-               ctx->bytes_remaining = phdr->connection_length;
-               break;
        case PARSERSTRING_NAME:
                ctx->curr = ctx->data + phdr->name_offset;
                ctx->bytes_remaining = phdr->name_length;
-- 
git-series 0.9.1
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel