summaryrefslogtreecommitdiff
authorDan Williams <dcbw@redhat.com>2009-10-03 06:33:18 (GMT)
committer Dan Williams <dcbw@redhat.com>2009-10-03 06:33:18 (GMT)
commitaa78b5f5e5319e04f5b57f928bfab69dd4b93d88 (patch) (side-by-side diff)
treeca8ca54a2688a30bdd7d0c6b8f15ecc88f9c76f5
parented059286c5361bf4dfa849088ee16c04cd075e51 (diff)
downloadModemManager-aa78b5f5e5319e04f5b57f928bfab69dd4b93d88.zip
ModemManager-aa78b5f5e5319e04f5b57f928bfab69dd4b93d88.tar.gz
bluetooth: handle rfcomm device moves
rfcomm devices seem to be created as 'virtual' devices first, without any parents, then moved to the right place in the device tree. So handle moves too; if the modem was already found in the 'add' phase it'll be ignored in the move phase.
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--src/mm-manager.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mm-manager.c b/src/mm-manager.c
index a812c79..7318914 100644
--- a/src/mm-manager.c
+++ b/src/mm-manager.c
@@ -612,7 +612,7 @@ handle_uevent (GUdevClient *client,
/* We only care about tty/net devices when adding modem ports,
* but for remove, also handle usb parent device remove events
*/
- if (!strcmp (action, "add") && strcmp (subsys, "usb") !=0 )
+ if ((!strcmp (action, "add") || !strcmp (action, "move")) && strcmp (subsys, "usb") !=0 )
device_added (self, device);
else if (!strcmp (action, "remove"))
device_removed (self, device);