diff --git a/[refs] b/[refs]
index 9a6aacbbe213..520a70702a4d 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 59f979455d7209171ab10a72c8df5c2512976cb4
+refs/heads/master: c751134ef8b070070d5f06348286b29d86424677
diff --git a/trunk/kernel/sched/features.h b/trunk/kernel/sched/features.h
index de00a486c5c6..c38f52ea53dd 100644
--- a/trunk/kernel/sched/features.h
+++ b/trunk/kernel/sched/features.h
@@ -11,14 +11,6 @@ SCHED_FEAT(GENTLE_FAIR_SLEEPERS, true)
  */
 SCHED_FEAT(START_DEBIT, true)
 
-/*
- * Based on load and program behaviour, see if it makes sense to place
- * a newly woken task on the same cpu as the task that woke it --
- * improve cache locality. Typically used with SYNC wakeups as
- * generated by pipes and the like, see also SYNC_WAKEUPS.
- */
-SCHED_FEAT(AFFINE_WAKEUPS, true)
-
 /*
  * Prefer to schedule the task we woke last (assuming it failed
  * wakeup-preemption), since its likely going to consume data we