On 08.10.2024 10:43, Wolfram Sang wrote: > >> Yes, hopefully this week. > > Reviewing and testing now. What tests did you run? > Of course compile-tested the series. Functional test cases: - Create device from userspace - Delete device from userspace - Delete adapter (by removing adapter driver module) and check that userspace-created client device has been auto-removed Driver auto-detection I couldn't check due to missing hw.
- References:
- [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Heiner Kallweit
- Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Wolfram Sang
- Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Heiner Kallweit
- Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Wolfram Sang
- Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- From: Wolfram Sang
- [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- Prev by Date: [PATCH 2/8] ASoC: SOF: ipc4-topology: Use local variables in sof_ipc4_init_input_audio_fmt()
- Next by Date: [PATCH v2] ASoC: dapm: avoid container_of() to get component
- Previous by thread: Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- Next by thread: Re: [PATCH v2 0/4] i2c: Replace lists of special clients with flagging of such clients
- Index(es):
 |