On Mon, Dec 04, 2023 at 04:40:55PM +0300, Dan Carpenter wrote: > On Mon, Dec 04, 2023 at 12:59:52PM +0000, Mark Brown wrote: > > ’ has no member named ‘jd_mutex’ > > 3312 | mutex_unlock(&rt5645->jd_mutex); > > | ^~ > I'm so puzzled by this. I'm on linux-next for Dec 4. I don't see > anything which would affect this on lore... Well, apart from anything else the mutex you're adding this for isn't present in the branch that has the commit that you're identifying as being fixed...
Attachment:
signature.asc
Description: PGP signature
- References:
- [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- From: Dan Carpenter
- Re: [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- From: Mark Brown
- Re: [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- From: Dan Carpenter
- [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- Prev by Date: Re: [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- Next by Date: Re: [PATCH 1/2] ASoC: ops: add correct range check for limiting volume
- Previous by thread: Re: [PATCH] ASoC: rt5650: add a missing unlock in rt5645_jack_detect_work()
- Next by thread: [PATCH] ASoC: audio-graph-card2: fix off by one in graph_parse_node_multi_nm()
- Index(es):