All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Yahya Toubali <yahya@yahyatoubali.me>,
	Shuah Khan <skhan@linuxfoundation.org>,
	"open list:PROC FILESYSTEM" <linux-kernel@vger.kernel.org>,
	"open list:PROC FILESYSTEM" <linux-fsdevel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Cc: Yahya Toubali <yahya@yahyatoubali.me>
Subject: Re: [PATCH v3] Documentation: proc: fix repeated word 'page'
Date: Wed, 22 Jul 2026 10:17:08 -0600	[thread overview]
Message-ID: <87fr1bc83f.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260718165613.1923550-1-yahya@yahyatoubali.me>

Yahya Toubali <yahya@yahyatoubali.me> writes:

> Remove the duplicate 'page' in the sentence describing large page
> allocation accounting. The extra word makes the description confusing.
>
> Signed-off-by: Yahya Toubali <yahya@yahyatoubali.me>
> ---
>  Documentation/filesystems/proc.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 2ccd5b2dfdd3..d22ac0addd42 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -513,7 +513,7 @@ In some kernel configurations, the semantics of pages part of a larger
>  allocation (e.g., THP) can differ: a page is accounted as "private" if all
>  pages part of the corresponding large allocation are *certainly* mapped in the
>  same process, even if the page is mapped multiple times in that process. A
> -page is accounted as "shared" if any page page of the larger allocation
> +page is accounted as "shared" if any page of the larger allocation
>  is *maybe* mapped in a different process. In some cases, a large allocation

Applied, thanks.

jon

      reply	other threads:[~2026-07-22 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 16:56 [PATCH v3] Documentation: proc: fix repeated word 'page' Yahya Toubali
2026-07-22 16:17 ` 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=87fr1bc83f.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yahya@yahyatoubali.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.