OSDN Git Service

greybus: eliminate extra response flag definitions
authorAlex Elder <elder@linaro.org>
Thu, 7 May 2015 18:03:52 +0000 (13:03 -0500)
committerGreg Kroah-Hartman <gregkh@google.com>
Thu, 7 May 2015 20:57:31 +0000 (22:57 +0200)
commit6d653370c0a67ff9b9b0d8249182d537859b528c
treea7522c75f35a67ff55202eddb1b3f61809e551ab
parent5c58640d8d66504c43c062e6e7d4ed0ade6bde9e
greybus: eliminate extra response flag definitions

All protocols use the same value to distinguish between request and
response message types.  This is a requirement.

Use GB_MESSAGE_TYPE_RESPONSE rather than GB_OPERATION_TYPE_RESPONSE
for the name of the flag used to distiguish between request and
response messages.

Get rid of the redundant response flag definitions that are
associated with specific protocols.

Describe the symbolic values as "operation types" rather than
"message types" where they are defined.  The message type for a
request is the same as the operation type; the message type for a
response is the operation type OR'd with GB_MESSAGE_TYPE_RESPONSE.

Signed-off-by: Alex Elder <elder@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
drivers/staging/greybus/gpbridge.h
drivers/staging/greybus/hid.c
drivers/staging/greybus/operation.c
drivers/staging/greybus/operation.h
drivers/staging/greybus/spi.c
drivers/staging/greybus/uart.c
drivers/staging/greybus/vibrator.c