bruns added a comment.
In D13216#397326 <https://phabricator.kde.org/D13216#397326>, @smithjd wrote: > "Locking" the scheduler is simpler here than identifying that it "has gone idle". "Locking" only happens here for a small number of runnables (two) that can't run concurrently. If you don't understand the code, do not change it. This is not about avoiding to be scheduled, but missing the schedule signal. You are mixing a ton of different things here, clean it up! REPOSITORY R293 Baloo REVISION DETAIL https://phabricator.kde.org/D13216 To: smithjd, bruns, mgallien Cc: ngraham, kde-frameworks-devel, #baloo, ashaposhnikov, michaelh, astippich, spoorun, bruns, abrahams
