greybus: record type in operation structure

Browse source

I've gone back and forth on this, but now that I'm looking at
asynchronous operations I know that the asynchronous callback will
want to know what type of operation it is handling, and right now
that's only available in the message header.

So record an operation's type in the operation structure, and use
it in a few spots where the header type was being used previously.
Pass the type to gb_operation_create_incoming() so it can fill
it in after the operation has been created.

Clean up the crap comments above the definition of the operation
structure.

Signed-off-by: Alex Elder <elder@linaro.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

...

This commit is contained in:

Alex Elder 2014-12-03 12:27:46 -06:00 • committed by Greg Kroah-Hartman

parent 746e0ef95a

commit 82b5e3feb7

2 changed files with 33 additions and 37 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

32

drivers/staging/greybus/operation.c

View file

38

drivers/staging/greybus/operation.h

View file