public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Dennis Lam <dennis.lamerice@gmail.com>, chris@chrisdown.name
Cc: Dennis Lam <dennis.lamerice@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs:core-api: fixed typos and grammar in printk-index page
Date: Tue, 07 May 2024 08:01:54 -0600	[thread overview]
Message-ID: <87zft1g1pp.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240502212522.4263-1-dennis.lamerice@gmail.com>

Dennis Lam <dennis.lamerice@gmail.com> writes:

> Signed-off-by: Dennis Lam <dennis.lamerice@gmail.com>
> ---
>  Documentation/core-api/printk-index.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/core-api/printk-index.rst b/Documentation/core-api/printk-index.rst
> index 3062f37d119b..1979c5dd32fe 100644
> --- a/Documentation/core-api/printk-index.rst
> +++ b/Documentation/core-api/printk-index.rst
> @@ -4,7 +4,7 @@
>  Printk Index
>  ============
>  
> -There are many ways how to monitor the state of the system. One important
> +There are many ways to monitor the state of the system. One important
>  source of information is the system log. It provides a lot of information,
>  including more or less important warnings and error messages.
>  
> @@ -101,7 +101,7 @@ their own wrappers adding __printk_index_emit().
>  
>  Only few subsystem specific wrappers have been updated so far,
>  for example, dev_printk(). As a result, the printk formats from
> -some subsystes can be missing in the printk index.
> +some subsystems can be missing in the printk index.
>  
Applied, thanks.

jon

      reply	other threads:[~2024-05-07 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 21:25 [PATCH] docs:core-api: fixed typos and grammar in printk-index page Dennis Lam
2024-05-07 14:01 ` 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=87zft1g1pp.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=chris@chrisdown.name \
    --cc=dennis.lamerice@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