mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>,
	suzuki.poulose@arm.com, mike.leach@linaro.org,
	james.clark@linaro.org, skhan@linuxfoundation.org
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>
Subject: Re: [PATCH] docs: fix "incase" typo in coresight/panic.rst
Date: Mon, 19 May 2025 05:42:17 -0600	[thread overview]
Message-ID: <87frh0kesm.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250513110931.15072-1-hendrik.hamerlinck@hammernet.be>

Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be> writes:

> Corrects a spelling mistake in Documentation/trace/coresight/panic.rst
> where "incase" was used instead of "in case".
>
> Signed-off-by: Hendrik Hamerlinck <hendrik.hamerlinck@hammernet.be>
> ---
>  Documentation/trace/coresight/panic.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/trace/coresight/panic.rst b/Documentation/trace/coresight/panic.rst
> index a58aa914c241..6e4bde953cae 100644
> --- a/Documentation/trace/coresight/panic.rst
> +++ b/Documentation/trace/coresight/panic.rst
> @@ -67,8 +67,8 @@ Trace data captured at the time of panic, can be read from rebooted kernel
>  or from crashdump kernel using a special device file /dev/crash_tmc_xxx.
>  This device file is created only when there is a valid crashdata available.
>  
> -General flow of trace capture and decode incase of kernel panic
> -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +General flow of trace capture and decode in case of kernel panic
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  1. Enable source and sink on all the cores using the sysfs interface.

Applied, thanks.

jon

      reply	other threads:[~2025-05-19 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 11:09 Hendrik Hamerlinck
2025-05-19 11:42 ` 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=87frh0kesm.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=coresight@lists.linaro.org \
    --cc=hendrik.hamerlinck@hammernet.be \
    --cc=james.clark@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=skhan@linuxfoundation.org \
    --cc=suzuki.poulose@arm.com \
    /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

all inboxes | Powered by JetHome®