ModemManager patch to make state change signal argument order consistent with doc

The order of the arguments in the state change signal is the opposite of how it is documented. They need to be consistent. I'd prefer to change the code to be consistent with the documentation (as in the attached patch). -Jason 0001-make-state-change-signal-consisten-with-doc.patch Description: B

ModemManager: Allow plugin to specify custom replies (was: ModemManager: Handle partial replies in AT+CPIN? (READY without OK))

Hi all, > So we have this "AirLink Fastrack Xtend" Sierra Wireless modem [1], > ModemManager uses the generic GSM plugin to handle it. > > On PIN check the following flow happens: > --> 'AT+CPIN?' > <-- '+CPIN: READY' > (see [2] for the logs reported by Thomas Bechtold a while ago). > > Once