public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Karan Sanghavi <karansanghvi98@gmail.com>,
	Karan Sanghavi <karansanghvi98@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Karan Sanghavi <karansanghvi98@gmail.com>
Subject: Re: [PATCH] Documentation: core-api: Fixed Typo error
Date: Wed, 07 Aug 2024 12:56:51 -0600	[thread overview]
Message-ID: <87le18rwjw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <ZqqHMIKdcNRVgAFd@Emma>

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

      reply	other threads:[~2024-08-07 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 18:49 [PATCH] Documentation: core-api: Fixed Typo error Karan Sanghavi
2024-08-07 18:56 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le18rwjw.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=karansanghvi98@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox