From: "Günther Noack" <gnoack3000@gmail.com>
To: Alejandro Colomar <alx+linux-man@kernel.org>
Cc: "Günther Noack" <gnoack3000@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH v3 0/1] {unix,socket,bind}.7: General Unix Domain Socket fixes
Date: Fri, 20 Nov 2026 14:25:34 +0100 [thread overview]
Message-ID: <20261120132535.20557-1-gnoack3000@gmail.com> (raw)
Hello!
This is patch set (A) spun off from the "Documentation fixes in
unix(7)" patch set [1], which is now split into these three parts:
(A) Miscellaneous fixes, mostly in unix.7, one in socket.7 <-- this one
(B) Socket options and Socket-level Control Messages (SCM_*)
(C) sock_diag.7
This patch set fixes miscellaneous inaccuracies and documents missing
error codes. It applies cleanly on the current "master".
Thank you for your reviews of v1 and v2 of the still-joined patch set,
as well as of v1 of the split patch set.
Changes in v3 (split):
* Mention EADDRINUSE in commit message for error code patch.
* Dropped already-merged commits (all but the one about error codes)
Changes in v2 (split):
* Mention commit hashes in commit messages, not in groff comments
* In SIOCINQ docs, describe SOCK_STREAM and SOCK_SEQPACKET together
* s/Named Unix Domain Sockets/pathname Unix Domain Sockets/
* Abstract namespaces: Wording simplifications
* Error descriptions: Wording simplifications
* Dropped commits:
* Drop the commit that documented SOCK_RAW as alias for SOCK_DGRAM
* Drop the commit that documented the socket() "protocol" argument 0
is acceptable to avoid EPROTONOSUPPORT
* Drop commits that already made it into the master branch.
Changes in v1 (split):
* Some commit message rewording (especially quoted the kernel code
more directly).
* In the Abstract UDS scoping commit below, reworded the subsequent
paragraph sligthly to avoid confusion with the "namespace"
terminology being used differently in adjacent paragraphs.
* I removed the commit that changed the wording about Out-of-Band
messaging, per Kuniyuki's suggestion in [2].
v1: https://lore.kernel.org/all/20261021210800.27338-2-gnoack3000@gmail.com/
v2: https://lore.kernel.org/all/20261103202136.13574-1-gnoack3000@gmail.com/
This patch set has been produced with the help of a LLM, which was
helpful for spotting a long list of inaccuracies, comparing the
documentation with the kernel implementation. (More details in [1])
–Günther
[1] https://lore.kernel.org/all/20261018173712.27670-1-gnoack3000@gmail.com/
[2] https://lore.kernel.org/all/CAAVpQUBh+J-aBLbkpzT7qmt7B714O529HWcTuQsVLT4wLBnDJA@mail.gmail.com/
Günther Noack (1):
man/man7/unix.7: ERRORS: Document EACCES, EAGAIN, EMSGSIZE, ENOSPC,
and EPERM
man/man7/unix.7 | 36 ++++++++++++++++++++++++++++++++++--
1 file changed, 34 insertions(+), 2 deletions(-)
--
2.56.1
next reply other threads:[~2026-11-20 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 13:25 Günther Noack [this message]
2026-11-20 13:25 ` [PATCH v3 1/1] man/man7/unix.7: ERRORS: Document EACCES, EAGAIN, EMSGSIZE, ENOSPC, and EPERM Günther Noack
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=20261120132535.20557-1-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--cc=alx+linux-man@kernel.org \
--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