From: Alejandro Colomar <alx@kernel.org>
To: astian <astian@memeware.net>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH v2] man/man5/proc_ioports.5: wfix
Date: Sun, 11 Oct 2026 19:11:31 +0200 [thread overview]
Message-ID: <asvDL7IokH085ojJ@debian> (raw)
In-Reply-To: <20260918070346.1407544-1-astian@memeware.net>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi astian,
> Date: 2026-09-18 07:03:12+0000
> From: astian <astian@memeware.net>
>
> Signed-off-by: astian <astian@memeware.net>
> ---
Thanks! I've applied the patch.
Have a lovely night!
Alex
> man/man5/proc_ioports.5 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man5/proc_ioports.5 b/man/man5/proc_ioports.5
> index 10d03f5aae7a..6729a7b98054 100644
> --- a/man/man5/proc_ioports.5
> +++ b/man/man5/proc_ioports.5
> @@ -10,7 +10,7 @@ .SH NAME
> .SH DESCRIPTION
> .TP
> .I /proc/ioports
> -This is a list of currently registered Input-Output port regions that
> +This is a list of currently registered input/output port regions that
> are in use.
> .SH SEE ALSO
> .BR proc (5)
> --
> 2.55.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-10-11 17:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 22:00 ioperm(2): confusing terminology astian
2026-09-12 22:24 ` Alejandro Colomar
2026-09-12 22:48 ` Alejandro Colomar
2026-09-13 6:29 ` astian
2026-09-14 12:56 ` Alejandro Colomar
2026-09-15 15:39 ` Markdown as a "less hairy" source format for man pages (was: ioperm(2): confusing terminology) G. Branden Robinson
2026-09-17 7:05 ` Markdown as a "less hairy" source format for man pages astian
2026-09-17 7:04 ` ioperm(2): confusing terminology astian
2026-09-17 11:00 ` Alejandro Colomar
2026-09-17 19:09 ` astian
2026-09-17 19:34 ` Alejandro Colomar
2026-09-17 6:16 ` [PATCH 1/2] man/man2/ioperm.2: Reword slightly for clarity astian
2026-09-17 11:59 ` Alejandro Colomar
2026-09-17 6:16 ` [PATCH 2/2] man/man2/ioperm.2: wfix astian
2026-09-17 11:59 ` Alejandro Colomar
2026-09-17 12:38 ` ioperm(2): confusing terminology G. Branden Robinson
2026-09-17 13:18 ` Alejandro Colomar
2026-09-17 19:08 ` astian
2026-09-17 23:02 ` G. Branden Robinson
2026-09-17 19:11 ` [PATCH 2/2] man/man2/ioperm.2: wfix astian
2026-09-17 19:58 ` [PATCH] man/man5/proc_ioports.5: wfix astian
2026-09-17 23:09 ` G. Branden Robinson
2026-09-17 23:16 ` Alejandro Colomar
2026-09-18 7:03 ` [PATCH v2] " astian
2026-10-11 17:11 ` Alejandro Colomar [this message]
2026-09-17 19:57 ` [PATCH v2] man/man2/ioperm.2: wfix astian
2026-10-11 17:12 ` Alejandro Colomar
2026-10-11 17:13 ` Alejandro Colomar
2026-10-11 20:25 ` astian
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=asvDL7IokH085ojJ@debian \
--to=alx@kernel.org \
--cc=astian@memeware.net \
--cc=linux-man@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