diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2017-09-26 09:53:05 +0200 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2017-09-26 10:03:17 +0200 |
| commit | 1e318bec54da3f37901eadb2a04a4520737eb9a0 (patch) | |
| tree | 86e5b7bf2b4bef0b039336697a288923925ac741 /examples/sms-python | |
| parent | 9f9c88a72a848603e8898f8faaf48497aa545525 (diff) | |
broadband-bearer: fix object types in connect_3gpp() steps
All the steps in the connect_3gpp() sequence are implemented as
methods in the MMBroadbandBearer class, and therefore the objects
received in the corresponding ready() methods are all bearers, not
modems.
This issue wasn't found before because the objects received were not
really being used after all, as we were relying on the ones kept in
the context or lately in the GTask itself.
Diffstat (limited to 'examples/sms-python')
0 files changed, 0 insertions, 0 deletions