From: Kir Kolyshkin <kolyshkin@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Kir Kolyshkin <kolyshkin@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 01/16] cacheflush.2: fix section reference
Date: Mon, 17 Jun 2024 16:10:13 -0700 [thread overview]
Message-ID: <20240617231035.1766780-2-kolyshkin@gmail.com> (raw)
In-Reply-To: <20240617231035.1766780-1-kolyshkin@gmail.com>
There is a reference to NOTES section, which no longer exists since
the commit 4131356cd ("man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY:
Reorganize sections").
Fixes: 4131356cd ("man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY: Reorganize sections")
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
---
man/man2/cacheflush.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man2/cacheflush.2 b/man/man2/cacheflush.2
index bc38355e6..0e3b4ac62 100644
--- a/man/man2/cacheflush.2
+++ b/man/man2/cacheflush.2
@@ -18,7 +18,7 @@ .SH SYNOPSIS
.P
.IR Note :
On some architectures,
-there is no glibc wrapper for this system call; see NOTES.
+there is no glibc wrapper for this system call; see VERSIONS.
.SH DESCRIPTION
.BR cacheflush ()
flushes the contents of the indicated cache(s) for the
--
2.45.2
next prev parent reply other threads:[~2024-06-17 23:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 23:10 [PATCH 00/16] man2: fix wrong/non-existent section references Kir Kolyshkin
2024-06-17 23:10 ` Kir Kolyshkin [this message]
2024-06-17 23:10 ` [PATCH 02/16] clone.2: fix wrong section reference Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 03/16] execve.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 04/16] gethostname.2: fix " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 05/16] getpriority.2: move info from NOTES to HISTORY Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 06/16] gettimeofday.2: fix wrong section reference Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 07/16] ioperm.2: " Kir Kolyshkin
2024-06-18 13:32 ` Alejandro Colomar
2024-06-18 17:35 ` [PATCH v2 " Kir Kolyshkin
2024-06-18 18:49 ` Alejandro Colomar
2024-06-17 23:10 ` [PATCH 08/16] kill.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 09/16] mkdir.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 10/16] mmap.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 11/16] nice.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 12/16] open.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 13/16] readdir.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 14/16] semctl.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 15/16] uname.2: " Kir Kolyshkin
2024-06-17 23:10 ` [PATCH 16/16] wait.2: " Kir Kolyshkin
2024-06-18 13:42 ` [PATCH 00/16] man2: fix wrong/non-existent section references 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=20240617231035.1766780-2-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