public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, наб <nabijaczleweli@nabijaczleweli.xyz>
Subject: Re: [PATCH v1 0/1] futex_waitv.2: Move text to a new PARAMETERS section
Date: Wed, 18 Feb 2026 22:28:13 +0100	[thread overview]
Message-ID: <aZYuPv3a1ONEi_nB@devuan> (raw)
In-Reply-To: <20260218204012.nzeqnwfgi2vdyi5n@illithid>

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

Hi Branden, наб,

On 2026-02-18T14:40:12-0600, G. Branden Robinson wrote:
> At 2026-02-18T21:30:53+0100, наб wrote:
> > On Wed, Feb 18, 2026 at 09:26:38PM +0100, Alejandro Colomar wrote:
> > > On 2026-02-18T21:16:06+0100, наб wrote:
> > > > On Wed, Feb 18, 2026 at 01:41:38AM +0100, Alejandro Colomar wrote:
> > > > > Please let me know what you think of this patch?
> > > > > Here's how the patch changes the page:
> > > [...]
> > > > > What do you think?  I think the formatted page is more readable.
> > > > I really hate it.
> > > Okay.  Do you like any part, or is it all hateful?  :-)
> > The format annoys me, the layout infuriates me, I find the tone
> > insulting.
> 
> When dealing with formally complex (meaning: decomposable) proposals,
> rapprochement is difficult with a binary oracle.
> 
> Alex,
> 
> The onus might be on you to correspondingly decompose наб's black box.
> 
> Some obvious candidates include the two hunks of the end of the
> diff of the formatted document that change only a few words, and the
> existence of a "PARAMETERS" section of the page.

Hmmm, I've now pushed a much smaller change:

	$ MANWIDTH=64 diffman-git HEAD
	--- HEAD^:man/man2/futex_waitv.2
	+++ HEAD:man/man2/futex_waitv.2
	@@ -54,11 +54,16 @@ DESCRIPTION
	      Futex words to monitor are given by struct futex_waitv,
	      whose fields are analogous to FUTEX_WAIT(2const) parame‐
	      ters, except .__reserved must be 0 and .flags must contain
	-     one of FUTEX2_SIZE_* ORed with some of the flags below.
	+     exactly one size flag, ORed with some other flags.
	 
	      FUTEX2_SIZE_U32
		     .val and .uaddr[] are 32‐bit unsigned integers.
	 
	+     FUTEX2_SIZE_U8
	+     FUTEX2_SIZE_U16
	+     FUTEX2_SIZE_U64
	+            These are defined, but not supported (EINVAL).
	+
	      FUTEX2_NUMA
		     The futex word is followed by another word of the
		     same size (.uaddr points to uintN_t[2] rather than
	@@ -132,9 +137,8 @@ ERRORS
		     Any waiters[].flags field contains an unknown flag.
	 
	      EINVAL
	-            Any waiters[].flags field is missing a FU‐
	-            TEX2_SIZE_* flag or has a size flag different than
	-            FUTEX2_SIZE_U32 set.
	+            Any waiters[].flags field does not contain exactly
	+            one size flag, or it contains an unsupported one.
	 
	      EINVAL
		     Any waiters[].__reserved field is not 0.

I think this one should be uncontroversial.


Cheers,
Alex

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

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

  reply	other threads:[~2026-02-18 21:28 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 12:49 [PATCH] futex_waitv.2: new page наб
2026-02-07 18:57 ` Alejandro Colomar
2026-02-07 19:16   ` наб
2026-02-07 21:50     ` Alejandro Colomar
2026-02-07 22:00 ` [PATCH v2] " наб
2026-02-09 22:35   ` Alejandro Colomar
2026-02-10 14:17     ` наб
2026-02-10 14:30       ` Alejandro Colomar
2026-02-10 15:54         ` Kristoffer Haugsbakk
2026-02-10 18:39           ` Alejandro Colomar
2026-02-11  7:35           ` Jeff King
2026-02-11  8:15             ` Kristoffer Haugsbakk
2026-02-11 15:43             ` Junio C Hamano
2026-02-10 16:54         ` Junio C Hamano
2026-02-10 17:11           ` Kristoffer Haugsbakk
2026-02-10 18:44           ` Alejandro Colomar
2026-02-10 20:05   ` Alejandro Colomar
2026-02-10 20:32     ` [PATCH v3] " наб
2026-02-10 21:11       ` Alejandro Colomar
2026-02-11  4:00         ` [PATCH v4] " наб
2026-02-11 13:23           ` Alejandro Colomar
2026-02-11 13:51             ` [PATCH v5] " наб
2026-02-11 14:15               ` [PATCH v6] " наб
2026-02-11 14:31                 ` Alejandro Colomar
2026-02-11 14:44                   ` [PATCH v7] " наб
2026-02-11 14:55                     ` Alejandro Colomar
2026-02-11 14:59                       ` наб
2026-02-11 15:13                         ` Alejandro Colomar
2026-02-14 17:32                     ` Alejandro Colomar
2026-02-14 19:30                       ` [PATCH v8] " наб
2026-02-14 20:03                         ` Alejandro Colomar
2026-02-14 20:48                           ` [PATCH v9] " наб
2026-02-15 18:18                             ` Alejandro Colomar
2026-02-15 19:00                               ` [PATCH v10] " наб
2026-02-16  0:32                                 ` Alejandro Colomar
2026-02-16 14:20                                   ` [PATCH v11] " наб
2026-02-16 14:50                                     ` Alejandro Colomar
2026-02-16 20:43                                       ` [PATCH v12] " наб
2026-02-17 13:07                                         ` Alejandro Colomar
2026-02-17 14:31                                           ` [PATCH v13] " наб
2026-02-17 15:46                                             ` Alejandro Colomar
2026-02-17 16:17                                               ` наб
2026-02-18  0:31                                                 ` Alejandro Colomar
2026-02-11 14:28               ` [PATCH v5] " Alejandro Colomar
2026-02-18  0:41 ` [PATCH v1 0/1] futex_waitv.2: Move text to a new PARAMETERS section Alejandro Colomar
2026-02-18  0:41   ` [PATCH v1 1/1] man/man2/futex_waitv.2: " Alejandro Colomar
2026-02-18 20:16   ` [PATCH v1 0/1] futex_waitv.2: " наб
2026-02-18 20:26     ` Alejandro Colomar
2026-02-18 20:30       ` наб
2026-02-18 20:33         ` Alejandro Colomar
2026-02-18 20:40         ` G. Branden Robinson
2026-02-18 21:28           ` Alejandro Colomar [this message]
2026-02-18 22:04             ` Alejandro Colomar

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=aZYuPv3a1ONEi_nB@devuan \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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