On Thu, 5 Jan 2023 at 01:42, Takashi Iwai <tiwai@xxxxxxx> wrote: fb425e1121ceef2b9d1b3ffccc195d55707 > > Oh, did you test with 6.2-rc? I checked the reverts only on top of > the 6.1.0. From there, you can revert all mentioned commits cleanly > and should build. > I was basing everything on 6.1.2 > In anyway, do I understand correctly that the bug still persists at > the revert of the commit 2be79d58645465351af5320eb14c70a94724c5ef, and > it's fixed by the revert of ac5e2fb425e1121ceef2b9d1b3ffccc195d55707? Yes that is correct. > > If so, what happens if you revert only > ac5e2fb425e1121ceef2b9d1b3ffccc195d55707? > I just tested this, and that also fixes the issue. -- Michael