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 <myro@myromyro.com>
Subject: Re: [PATCH] docs: proc: fix minor grammar and formatting issues
Date: Mon, 27 Apr 2026 04:03:15 -0600 [thread overview]
Message-ID: <87fr4gpvoc.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260415175230.46721-1-myro@myromyro.com>
Myro <mirademche@gmail.com> writes:
> Fix missing "from" in "prevent <pid> --from-- being reused" and
> add spacing in vm_area_struct range notation for readability.
>
> No functional changes. :)
> ---
> Documentation/filesystems/proc.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
The patch seems OK, but it needs a proper Signed-off-by line.
Thanks,
jon
next prev parent reply other threads:[~2026-04-27 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 17:52 [PATCH] docs: proc: fix minor grammar and formatting issues Myro
2026-04-27 10:03 ` 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-28 13:30 Myro
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=87fr4gpvoc.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