Documentation: core-api: Fixed Typo error
PATCH 1/1 Documentation: core-api: Fixed Typo error
Corrected the typographical of the word "instrumentation" in the below mentioned sentence.
Signed-off-by Karan Sanghavi <[email protected]>
--- Documentation/core-api/entry.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/core-api/entry.rst +1 -1
@@ -18,7 +18,7 @@ exceptions`_, `NMI and NMI-like exceptions`_. Non-instrumentable code - noinstr --------------------------------- -Most instrumentation facilities depend on RCU, so intrumentation is prohibited +Most instrumentation facilities depend on RCU, so instrumentation is prohibited for entry code before RCU starts watching and exit code after RCU stops watching. In addition, many architectures must save and restore register state, which means that (for example) a breakpoint in the breakpoint entry code would
Signature · 1 line
2.43.0
Jonathan Corbet
maintainerQuoted 13 lines · Karan Sanghavi
Corrected the typographical of the word "instrumentation" in the below mentioned sentence.
Signed-off-by Karan Sanghavi <[email protected]>--- Documentation/core-api/entry.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Documentation/core-api/entry.rst +0
-0
Documentation/core-api/entry.rst exceptions`_, `NMI and NMI-like exceptions`_. · line 23
Quoted 7 lines
Documentation/core-api/entry.rst +1
-1@@ -18,7 +18,7 @@ exceptions`_, `NMI and NMI-like exceptions`_. Non-instrumentable code - noinstr --------------------------------- -Most instrumentation facilities depend on RCU, so intrumentation is prohibited +Most instrumentation facilities depend on RCU, so instrumentation is prohibited for entry code before RCU starts watching and exit code after RCU stops watching. In addition, many architectures must save and restore register state,
Thanks for your patch, but this mistake was already fixed back in April for the 6.10 release.
jon