diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2026-05-26 11:22:30 +0200 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2026-06-02 12:26:09 +0200 |
| commit | c0404dd88d124714351f7a961d3313ee0f2f036b (patch) | |
| tree | b7ed6e10a51c828c37c20f1996aa4ab03b3ca85b /drivers/platform/wmi/tests/git@git.tavy.me:linux.git | |
| parent | ec9d4f1c424134bbf30965075df78d02a5d021dc (diff) | |
sched/proxy: Remove superfluous clear_task_blocked_in()
Per the discussion here:
https://lore.kernel.org/all/20260403112810.GG3738786@noisy.programming.kicks-ass.net/
The reason for this condition is that the signal condition in
try_to_block_task() would set_task_blocked_in_waking(). However, it no longer
does that, in fact, that path does clear_task_blocked_on().
Further, per the discussions here:
https://lore.kernel.org/r/dc61cf77-e541-441d-a708-c40e19aa0db2%40amd.com
https://lore.kernel.org/r//9dd1d24d-45d3-4ee2-8e67-8305b34bfb6d%40amd.com
there are a few other edge cases that needed this. But they're all
variants of PROXY_WAKING leaking out. And since PROXY_WAKING is now
gone, this is no longer needed either.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: John Stultz <jstultz@google.com>
Link: https://patch.msgid.link/20260526113322.120970670%40infradead.org
Diffstat (limited to 'drivers/platform/wmi/tests/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions