All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: astian <astian@memeware.net>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH 1/2] man/man2/ioperm.2: Reword slightly for clarity
Date: Thu, 17 Sep 2026 13:59:44 +0200	[thread overview]
Message-ID: <aqvWHiz44NxkDbPh@devuan> (raw)
In-Reply-To: <20260917062039.1365378-1-astian@memeware.net>

[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]

Hi astian,

> Date: 2026-09-17 06:16:00+0000
> From: astian <astian@memeware.net>
>
> Replace unexplained mention of "bits" (implicit reference to a
> kernel-maintained permissions bitmap) with "ports".
> 
> Link: <https://lore.kernel.org/linux-man/aqfsMbQWdqq_TG_b@devuan/T/>
> Signed-off-by: astian <astian@memeware.net>
> ---
> Didn't address your questions about general arch support and the
> EIO/ENOSYS on PowerPC.


Thanks!  I've applied patch 1/2.


Cheers,
Alex

> 
>  man/man2/ioperm.2 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/man/man2/ioperm.2 b/man/man2/ioperm.2
> index cb2c48652b5d..e4a058164f6f 100644
> --- a/man/man2/ioperm.2
> +++ b/man/man2/ioperm.2
> @@ -16,13 +16,13 @@ .SH SYNOPSIS
>  .fi
>  .SH DESCRIPTION
>  .BR ioperm ()
> -sets the port access permission bits for the calling thread for
> +sets the calling thread's access permission for
>  .I num
> -bits starting from port address
> +ports starting from port address
>  .IR from .
>  If
>  .I turn_on
> -is nonzero, then permission for the specified bits is enabled;
> +is nonzero, then permission for the specified ports is enabled;
>  otherwise it is disabled.
>  If
>  .I turn_on
> -- 
> 2.55.0
> 
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-09-17 11:59 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 [this message]
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
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=aqvWHiz44NxkDbPh@devuan \
    --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 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.