> - /* Remove devices instantiated from sysfs */ > - mutex_lock_nested(&adap->userspace_clients_lock, > - i2c_adapter_depth(adap)); > - list_for_each_entry_safe(client, next, &adap->userspace_clients, > - detected) { > - dev_dbg(&adap->dev, "Removing %s at 0x%x\n", client->name, > - client->addr); > - list_del(&client->detected); > - i2c_unregister_device(client); > - } > - mutex_unlock(&adap->userspace_clients_lock); Same question as previous patch: why no removal when adapter gets deleted?
Attachment:
signature.asc
Description: PGP signature
- References:
- [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Heiner Kallweit
- [PATCH v2 3/4] i2c: Replace list-based mechanism for handling userspace-created clients
- From: Heiner Kallweit
- [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- Prev by Date: Re: [PATCH v2 2/4] i2c: Replace list-based mechanism for handling auto-detected clients
- Next by Date: Re: [PATCH v2 4/4] i2c: core: Remove obsolete members of i2c_adapter and i2c_client
- Previous by thread: [PATCH v2 3/4] i2c: Replace list-based mechanism for handling userspace-created clients
- Next by thread: [PATCH v2 4/4] i2c: core: Remove obsolete members of i2c_adapter and i2c_client
- Index(es):
![]() |