| Summary: | [PATCH] mbm: wait until the E2NAP response for disconnecting | ||
|---|---|---|---|
| Product: | ModemManager | Reporter: | Lubomir Rintel <lkundrak> |
| Component: | general | Assignee: | ModemManager bug user <modemmanager> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git master | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Patch 1/2
Patch 2/2 |
||
Created attachment 123525 [details]
Patch 2/2
Patches look mostly good, except for really old F3507g device firmware. Those didn't support E2NAP indications, and that's why the polling was implemented. We should probably also poll for disconnect too. I implemented disconnect polling and waiting for the E2NAP response in the dcbw/mbm-connect-disconnect-cleanup branch. Could you review? Merged branch after review from Aleksander. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 123522 [details] Patch 1/2 Otherwise the client may start connecting again (such as NetworkManager on autoconnect retry) and the anychronous E2NAP may abort it.