s390/qeth: clarify parameter for simple assist cmds

Browse source

For code that uses qeth_send_simple_setassparms_prot(), we currently
can't differentiate whether the cmd should contain (1) no parameter, or
(2) a 4-byte parameter with value 0.
At the moment this doesn't cause any trouble. But when using dynamically
allocated cmds, we need to know whether to allocate & transmit an
additional 4 bytes of zeroes.
So instead of the raw parameter value, pass a parameter pointer
(or NULL) to qeth_send_simple_setassparms_prot().

Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Julian Wiedmann 2019-06-27 17:01:23 +02:00 • committed by David S. Miller

parent a59d121da2

commit 1c696c896f

4 changed files with 26 additions and 23 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

6

drivers/s390/net/qeth_core.h

View file

15

drivers/s390/net/qeth_core_main.c

View file

2

drivers/s390/net/qeth_core_mpc.h

View file

26

drivers/s390/net/qeth_l3_main.c

View file