public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Gopi Krishna Menon <krishnagopi487@gmail.com>
Cc: Gopi Krishna Menon <krishnagopi487@gmail.com>,
	dhowells@redhat.com, brauner@kernel.org,
	max.kellermann@ionos.com, skhan@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] docs: folio_queue: Fix minor typo in folio_queue page
Date: Tue, 12 Aug 2025 12:40:25 -0600	[thread overview]
Message-ID: <874iucfko6.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250810235346.4153-1-krishnagopi487@gmail.com>

Gopi Krishna Menon <krishnagopi487@gmail.com> writes:

> Specifically, fix typo 'hese'-> 'these'
>
> Signed-off-by: Gopi Krishna Menon <krishnagopi487@gmail.com>
> ---
>  Documentation/core-api/folio_queue.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/folio_queue.rst b/Documentation/core-api/folio_queue.rst
> index 83cfbc157e49..b7628896d2b6 100644
> --- a/Documentation/core-api/folio_queue.rst
> +++ b/Documentation/core-api/folio_queue.rst
> @@ -44,7 +44,7 @@ Each segment in the list also stores:
>   * the size of each folio and
>   * three 1-bit marks per folio,
>  
> -but hese should not be accessed directly as the underlying data structure may
> +but these should not be accessed directly as the underlying data structure may
>  change, but rather the access functions outlined below should be used.

Applied, thanks.

jon

      reply	other threads:[~2025-08-12 18:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 23:53 [PATCH] docs: folio_queue: Fix minor typo in folio_queue page Gopi Krishna Menon
2025-08-12 18:40 ` 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=874iucfko6.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=krishnagopi487@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.kellermann@ionos.com \
    --cc=skhan@linuxfoundation.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