[merged mm-nonmm-stable] hung_task-update-detect_hung_task_blocker-kconfig-help.patch removed from -mm tree

The quilt patch titled
     Subject: hung_task: update DETECT_HUNG_TASK_BLOCKER Kconfig help
has been removed from the -mm tree.  Its filename was
     hung_task-update-detect_hung_task_blocker-kconfig-help.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Xibo Wang <[email protected]>
Subject: hung_task: update DETECT_HUNG_TASK_BLOCKER Kconfig help
Date: Thu, 30 Jul 2026 14:18:54 +0800

The help text still says the feature only covers mutexes, but blocker
tracking has since been extended to semaphores and rwsems. Update the
description to match the supported lock types.

Link: https://lore.kernel.org/[email protected]
Cc: Petr Mladek <[email protected]>
Signed-off-by: Xibo Wang <[email protected]>
Suggested-by: Lance Yang <[email protected]>
Reviewed-by: Lance Yang <[email protected]>
Cc: "Masami Hiramatsu (Google)" <[email protected]>
Cc: Petr Mladek <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---

 lib/Kconfig.debug |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

--- a/lib/Kconfig.debug~hung_task-update-detect_hung_task_blocker-kconfig-help
+++ a/lib/Kconfig.debug
@@ -1320,10 +1320,10 @@ config DETECT_HUNG_TASK_BLOCKER
 	depends on !PREEMPT_RT
 	default y
 	help
-	  Say Y here to show the blocker task's stacktrace who acquires
-	  the mutex lock which "hung tasks" are waiting.
-	  This will add overhead a bit but shows suspicious tasks and
-	  call trace if it comes from waiting a mutex.
+	  Say Y here to show a possible blocker task's stacktrace when
+	  a hung task is waiting on a mutex, semaphore, or rwsem.
+	  This will add a bit of overhead but shows suspicious tasks and
+	  call traces for waits on one of these locks.
 
 config WQ_WATCHDOG
 	bool "Detect Workqueue Stalls"
_

Patches currently in -mm which might be from [email protected] are