Hi! > When the component level pin control functions were added they for some > no longer obvious reason handled adding prefixing of widget names. This > meant that when the lack of prefix handling in the DAPM level pin > operations was fixed by ae4fc532244b3bb4d (ASoC: dapm: use component > prefix when checking widget names) the one device using the component > level API ended up with the prefix being applied twice, causing all > lookups to fail. AFAICT ae4fc532244b3bb4d (ASoC: dapm: use component...) is not in 5.10-stable, so this one should not go into 5.10-stable, either? (Or alternatively, both can go in). I hope I understand it right. Best regards, Pavel -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Attachment:
signature.asc
Description: PGP signature
