The patch titled
Subject: rcu: update debugobjects fixup callbacks return type
has been removed from the -mm tree. Its filename was
rcu-update-debugobjects-fixup-callbacks-return-type.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: "Du, Changbin" <changbin.du@xxxxxxxxx>
Subject: rcu: update debugobjects fixup callbacks return type
Update the return type to use bool instead of int, corresponding to
cheange (debugobjects: make fixup functions return bool instead of int).
Signed-off-by: Du, Changbin <changbin.du@xxxxxxxxx>
Cc: Jonathan Corbet <corbet@xxxxxxx>
Cc: Josh Triplett <josh@xxxxxxxxxx>
Cc: Steven Rostedt <rostedt@xxxxxxxxxxx>
Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Cc: Tejun Heo <tj@xxxxxxxxxx>
Cc: Christian Borntraeger <borntraeger@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/rcu/update.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -puN kernel/rcu/update.c~rcu-update-debugobjects-fixup-callbacks-return-type kernel/rcu/update.c
--- a/kernel/rcu/update.c~rcu-update-debugobjects-fixup-callbacks-return-type
+++ a/kernel/rcu/update.c
@@ -386,7 +386,7 @@ void destroy_rcu_head(struct rcu_head *h
* - an unknown object is activated (might be a statically initialized object)
* Activation is performed internally by call_rcu().
*/
-static int rcuhead_fixup_activate(void *addr, enum debug_obj_state state)
+static bool rcuhead_fixup_activate(void *addr, enum debug_obj_state state)
{
struct rcu_head *head = addr;
@@ -399,9 +399,9 @@ static int rcuhead_fixup_activate(void *
*/
debug_object_init(head, &rcuhead_debug_descr);
debug_object_activate(head, &rcuhead_debug_descr);
- return 0;
+ return false;
default:
- return 1;
+ return true;
}
}
_
Patches currently in -mm which might be from changbin.du@xxxxxxxxx are
checkpatch-add-support-to-check-already-applied-git-commits.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
