public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Myro <mirademche@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, Myro Demma <myro@myromyro.com>
Subject: Re: [PATCH] docs: proc: fix minor grammar and formatting issues
Date: Sun, 03 May 2026 09:08:12 -0600	[thread overview]
Message-ID: <87fr48cyzn.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260428133001.11384-1-myro@myromyro.com>

Myro <mirademche@gmail.com> writes:

> From: Myro Demma <myro@myromyro.com>
>
> Fix missing "from" in "prevent <pid> being reused" and
> add spacing in vm_area_struct range notation for readability.
>
> No functional changes.
>
> Signed-off-by: Myro Demma <myro@myromyro.com>
> ---
>  Documentation/filesystems/proc.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
> index 873761087f8d..d828006bd91c 100644
> --- a/Documentation/filesystems/proc.rst
> +++ b/Documentation/filesystems/proc.rst
> @@ -118,7 +118,7 @@ PTRACE_MODE_ATTACH permissions; CAP_PERFMON capability does not grant access
>  to /proc/PID/mem for other processes.
>  
>  Note that an open file descriptor to /proc/<pid> or to any of its
> -contained files or subdirectories does not prevent <pid> being reused
> +contained files or subdirectories does not prevent <pid> from being reused
>  for some other process in the event that <pid> exits. Operations on
>  open /proc/<pid> file descriptors corresponding to dead processes
>  never act on any new process that the kernel may, through chance, have
> @@ -2199,7 +2199,7 @@ the process is maintaining.  Example output::
>       | lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls
>  
>  The name of a link represents the virtual memory bounds of a mapping, i.e.
> -vm_area_struct::vm_start-vm_area_struct::vm_end.
> +vm_area_struct::vm_start - vm_area_struct::vm_end.
>  

Applied, thanks.

jon

  reply	other threads:[~2026-05-03 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 13:30 [PATCH] docs: proc: fix minor grammar and formatting issues Myro
2026-05-03 15:08 ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-28 12:26 Myro
2026-04-28 12:49 ` Jonathan Corbet
2026-04-15 17:52 Myro
2026-04-27 10:03 ` Jonathan Corbet

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=87fr48cyzn.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=mirademche@gmail.com \
    --cc=myro@myromyro.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