| commit | c89ed09d025f08de1e78a85271543375c590fafd | |
| author | Tilman Schmidt <tilman@imap.cc> | |
| Mon, 21 Jun 2010 13:54:50 +0000 (21 13:54 +0000) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 2 Aug 2010 17:30:10 +0000 (2 10:30 -0700) | ||
| tree | c1df0711a2d4ac5e0f7dbaa48d7cb402c2630e3b | treesnapshot (tar.gz zip) |
| parent | 969d220fc2e66ad1a08c6df3f2381ce0b2b1cd05 | commitdiff |
isdn/gigaset: correct CAPI DATA_B3 Delivery Confirmation
commit 23b36778b4c82577746d26e4ac0ae66c6f462475 upstream.
The Gigaset CAPI driver handled all DATA_B3_REQ messages as if the
Delivery Confirmation flag bit was set, delaying the emission of the
DATA_B3_CONF reply until the data was actually transmitted. Some
CAPI applications (notably Asterisk) aren't happy with that
behaviour. Change it to actually evaluate the Delivery Confirmation
flag as described the CAPI specification.
Impact: bugfix
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 23b36778b4c82577746d26e4ac0ae66c6f462475 upstream.
The Gigaset CAPI driver handled all DATA_B3_REQ messages as if the
Delivery Confirmation flag bit was set, delaying the emission of the
DATA_B3_CONF reply until the data was actually transmitted. Some
CAPI applications (notably Asterisk) aren't happy with that
behaviour. Change it to actually evaluate the Delivery Confirmation
flag as described the CAPI specification.
Impact: bugfix
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/isdn/gigaset/capi.c | diffblobblamehistory |