https://bugzilla.kernel.org/show_bug.cgi?id=85491
--- Comment #18 from Marek <kordikmarek at gmail.com> --- It seemd weird also to me, that result of the bisect was a merge so I tried to build one of parents of this wrong merge commit (before Michael's comment) and then I was merging to the parent the other parents one by one: Parent: 518a6a34f645897ec3440e5cbcf53ced3493ee1c - good - I startded with this one Parent: 14574674e461077a9f4dd5eae050f622e8b8c084 - good - I merged this to the commit above Parent: 3cb30b73ad71b384c6289243d4ccd31ab90bce6f - good - I merged this to the commit above Parent: 034cd97ebda4062eb4402a6cf963ccd262caa86a - good - I merged this to the commit above Parent: 9edbcd2252b5ef148177c9f2c11a56469cf5db52 - good - I merged this to the commit above Parent: 67d29b5c6c40e91b124695e9250c2fd24915e24a - bad After Dave's comment I decided to merge commit 67d29b5c6c40e91b124695e9250c2fd24915e24a as the last. Based on this I think that it is possible that the commit we are looking for is one of commits between 67d29b5c6c40e91b124695e9250c2fd24915e24a and 0b2d70764bb39242dcc49c0ebd10fcb8258ce5fa -- You are receiving this mail because: You are watching the assignee of the bug.
