diff options
| author | Julian Wiedmann <jwi@linux.ibm.com> | 2019-06-27 18:01:23 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-06-27 20:18:23 +0300 |
| commit | 1c696c896f218b12d5f92d892fffee5abd0265c9 (patch) | |
| tree | 5e71283f227405533ec655bf77913dc8ecf310b7 /Documentation/bpf | |
| parent | a59d121da2394dcb84a42bf2fe436180ce2afe5c (diff) | |
| download | linux-1c696c896f218b12d5f92d892fffee5abd0265c9.tar.xz | |
s390/qeth: clarify parameter for simple assist cmds
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>
Diffstat (limited to 'Documentation/bpf')
0 files changed, 0 insertions, 0 deletions