From fd1edf592a26ee144c738c052b44f664bb67836c Mon Sep 17 00:00:00 2001 From: "Paul E. McKenney" Date: Tue, 7 Jun 2011 17:05:34 -0700 Subject: [PATCH] --- yaml --- r: 268950 b: refs/heads/master c: b15a2e7d16cc6f6082d8c6a85349e48588763ffc h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/RCU/NMI-RCU.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index e17b371ae296..c67a421758dc 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: bdf2a4364904d6cf2f59b16b0bd86fdc5a2c6152 +refs/heads/master: b15a2e7d16cc6f6082d8c6a85349e48588763ffc diff --git a/trunk/Documentation/RCU/NMI-RCU.txt b/trunk/Documentation/RCU/NMI-RCU.txt index bf82851a0e57..687777f83b23 100644 --- a/trunk/Documentation/RCU/NMI-RCU.txt +++ b/trunk/Documentation/RCU/NMI-RCU.txt @@ -95,7 +95,7 @@ not to return until all ongoing NMI handlers exit. It is therefore safe to free up the handler's data as soon as synchronize_sched() returns. Important note: for this to work, the architecture in question must -invoke irq_enter() and irq_exit() on NMI entry and exit, respectively. +invoke nmi_enter() and nmi_exit() on NMI entry and exit, respectively. Answer to Quick Quiz