Jacob Erlbeck 36153dc61a bssgp: Handle BSSGP STATUS messages ... Currently incoming BSSGP STATUS messages are just logged and no other action is taken. This makes it impossible for higher layers to react to failures which are indicated by corresponding STATUS messages unless a timeout is triggered as a result of that failure later on. This commit adds a bssgp_rx_status() function and calls it on incoming STATUS messages. That function logs a message, increments the new BSSGP_CTR_STATUS counter if the bctx context exists and invokes an NM_STATUS status indication. The latter will allow the application to handle failures immediately. Since all STATUS messages should be handled, the function is already called in bssgp_rcvmsg and the message is no longer handled in (and will not reach) bssgp_rx_sign and bssgp_rx_ptp. Ticket: OW#1414 Sponsored-by: On-Waves ehf		2015-03-18 21:54:37 +01:00
..
bssgp_fc_test.c	bssgp: Free msgb in case of error when calling into gprs_ns_sendmsg	2014-10-10 17:55:13 +02:00
bssgp_fc_tests.err	tests: Make the gb test work with srcdir != builddir	2012-09-11 11:49:35 +02:00
bssgp_fc_tests.ok	GPRS BSSGP test: integrate into autotest	2012-09-07 12:07:54 +02:00
bssgp_fc_tests.sh	GPRS BSSGP test: integrate into autotest	2012-09-07 12:07:54 +02:00
gprs_bssgp_test.c	bssgp: Handle BSSGP STATUS messages	2015-03-18 21:54:37 +01:00
gprs_bssgp_test.ok	bssgp: Handle BSSGP STATUS messages	2015-03-18 21:54:37 +01:00
gprs_ns_test.c	gprs-ns/test: Check the nsvc state explicitely	2014-10-09 16:08:44 +02:00
gprs_ns_test.ok	gprs-ns: Fix reset state handling	2014-10-09 07:52:43 +02:00