From: Kir Kolyshkin <kolyshkin@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Kir Kolyshkin <kolyshkin@gmail.com>
Subject: [PATCH] clone.2: refer to VERSIONS for raw clone prototype
Date: Wed, 23 Aug 2023 22:14:52 -0700 [thread overview]
Message-ID: <20230824051452.1293717-1-kolyshkin@gmail.com> (raw)
Commit 2a15a76bba35c ("clone.2: Document raw syscall interfaces on various other
architectures") adds this note:
/* For the prototype of the raw system call, see NOTES */
but places the raw syscall prototypes into DESCRIPTION.
Next, commit 1874193ebf07068b ("clone.2: Add NOTES heading") makes the
information to appear in NOTES.
Finally, commit 4131356cdab8d ("man*/, man-pages.7: VERSIONS, STANDARDS,
HISTORY: Reorganize sections") moves the NOTES section (with some but
not all of the old contents from NOTES and VERSIONS) down, and thus the
raw prototypes are now under VERSIONS.
Fix the comment accordingly.
Cc:
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
man2/clone.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/clone.2 b/man2/clone.2
index 4a75b557b..73ad5a6fa 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -58,7 +58,7 @@ Standard C library
.BI " void *_Nullable " tls ,
.BI " pid_t *_Nullable " child_tid " \fR*/\fP );"
.PP
-/* For the prototype of the raw clone() system call, see NOTES */
+/* For the prototype of the raw clone() system call, see VERSIONS */
.PP
.BR "#include <linux/sched.h>" " /* Definition of " "struct clone_args" " */"
.BR "#include <sched.h>" " /* Definition of " CLONE_* " constants */"
--
2.41.0
next reply other threads:[~2023-08-24 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 5:14 Kir Kolyshkin [this message]
2023-08-25 18:00 ` [PATCH] clone.2: refer to VERSIONS for raw clone prototype 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=20230824051452.1293717-1-kolyshkin@gmail.com \
--to=kolyshkin@gmail.com \
--cc=alx@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;
as well as URLs for NNTP newsgroup(s).