From: Alejandro Colomar <alx@kernel.org>
To: seth.i.mcdonald@gmail.com
Cc: Seth McDonald <sethmcmail@pm.me>, linux-man@vger.kernel.org
Subject: Re: [PATCH v1 1/4] man/man2/syscall.2: Add HISTORY section
Date: Wed, 31 Dec 2025 14:46:52 +0100 [thread overview]
Message-ID: <aVUpP9L6fk1-STyA@devuan> (raw)
In-Reply-To: <a2a2a51edeb0b23ebedf998cfac788dd96ee7ff3.1767072049.git.sethmcmail@pm.me>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Tue, Dec 30, 2025 at 04:42:00PM +1000, seth.i.mcdonald@gmail.com wrote:
> From: Seth McDonald <sethmcmail@pm.me>
>
> Move the description of syscall(2)'s first appearance from NOTES to a
> new HISTORY section.
>
> Signed-off-by: Seth McDonald <sethmcmail@pm.me>
Patch applied; Thanks!
Cheers,
Alex
> ---
> man/man2/syscall.2 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man/man2/syscall.2 b/man/man2/syscall.2
> index be645c0f4a..54385cdfba 100644
> --- a/man/man2/syscall.2
> +++ b/man/man2/syscall.2
> @@ -62,10 +62,11 @@ .SH ERRORS
> The requested system call number is not implemented.
> .P
> Other errors are specific to the invoked system call.
> -.SH NOTES
> +.SH HISTORY
> .BR syscall ()
> first appeared in
> 4BSD.
> +.SH NOTES
> .SS Architecture-specific requirements
> Each architecture ABI has its own requirements on how
> system call arguments are passed to the kernel.
> --
> 2.47.3
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-31 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 6:41 [PATCH v1 0/4] Miscellaneous fixes seth.i.mcdonald
2025-12-30 6:42 ` [PATCH v1 1/4] man/man2/syscall.2: Add HISTORY section seth.i.mcdonald
2025-12-31 13:46 ` Alejandro Colomar [this message]
2025-12-30 6:42 ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix seth.i.mcdonald
2025-12-30 6:59 ` Collin Funk
2025-12-30 7:18 ` Seth McDonald
2025-12-30 7:27 ` G. Branden Robinson
2025-12-30 7:40 ` Collin Funk
2025-12-30 7:53 ` G. Branden Robinson
2025-12-30 11:34 ` Alejandro Colomar
2025-12-30 7:22 ` Is 2.11BSD < 4BSD? It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix) G. Branden Robinson
2025-12-30 7:35 ` Is 2.11BSD < 4BSD? It depends Collin Funk
2025-12-31 13:46 ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix Alejandro Colomar
2025-12-30 6:42 ` [PATCH v1 3/4] man/man2/utime.2: SYNOPSIS: ffix seth.i.mcdonald
2025-12-31 13:45 ` Alejandro Colomar
2025-12-30 6:42 ` [PATCH v1 4/4] man/man2const/F_GETSIG.2const: HISTORY: tfix seth.i.mcdonald
2025-12-31 13:47 ` Alejandro Colomar
2025-12-31 13:48 ` [PATCH v1 0/4] Miscellaneous fixes 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=aVUpP9L6fk1-STyA@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=seth.i.mcdonald@gmail.com \
--cc=sethmcmail@pm.me \
/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;
as well as URLs for NNTP newsgroup(s).