Documentation/core-api/entry.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Corrected the typographical of the word "instrumentation"
in the below mentioned sentence.
Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com>
---
Documentation/core-api/entry.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/entry.rst b/Documentation/core-api/entry.rst
index e12f22ab3..a15f9b176 100644
--- a/Documentation/core-api/entry.rst
+++ b/Documentation/core-api/entry.rst
@@ -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
--
2.43.0
Karan Sanghavi <karansanghvi98@gmail.com> writes: > Corrected the typographical of the word "instrumentation" > in the below mentioned sentence. > > Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com> > --- > Documentation/core-api/entry.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/core-api/entry.rst b/Documentation/core-api/entry.rst > index e12f22ab3..a15f9b176 100644 > --- a/Documentation/core-api/entry.rst > +++ b/Documentation/core-api/entry.rst > @@ -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
© 2016 - 2026 Red Hat, Inc.