From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
linux-man@vger.kernel.org, posk@google.com, peterz@infradead.org,
mathieu.desnoyers@efficios.com, paulmck@kernel.org,
boqun.feng@gmail.com, linux-kernel@vger.kernel.org,
pjt@google.com, ckennelly@google.com, shuah@kernel.org,
posk@posk.io
Subject: [PATCH] membarrier.2: Update prototype
Date: Sun, 1 Nov 2020 21:04:41 +0100 [thread overview]
Message-ID: <20201101200440.17328-1-colomar.6.4.3@gmail.com> (raw)
The Linux kernel now uses 'flags' and added a new argument: 'cpu_id'.
These changes were introduced to the kernel
in commit 2a36ab717e8fe678d98f81c14a0b124712719840.
Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
---
man2/membarrier.2 | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/man2/membarrier.2 b/man2/membarrier.2
index 24a24ba86..42b7e2acc 100644
--- a/man2/membarrier.2
+++ b/man2/membarrier.2
@@ -23,6 +23,13 @@
.\" %%%LICENSE_END
.\"
.TH MEMBARRIER 2 2020-06-09 "Linux" "Linux Programmer's Manual"
+.\" FIXME:
+.\" The Linux kernel now uses 'flags' and added a new argument: 'cpu_id'.
+.\" These changes were introduced to the kernel
+.\" in commit 2a36ab717e8fe678d98f81c14a0b124712719840.
+.\" The prototype has been updated,
+.\" but the new features have not yet been documented.
+.\" TODO: Document those new features.
.SH NAME
membarrier \- issue memory barriers on a set of threads
.SH SYNOPSIS
@@ -30,7 +37,7 @@ membarrier \- issue memory barriers on a set of threads
.PP
.B #include <linux/membarrier.h>
.PP
-.BI "int membarrier(int " cmd ", int " flags ");"
+.BI "int membarrier(int " cmd ", unsigned int " flags ", int " cpu_id );
.fi
.PP
.IR Note :
--
2.28.0
next reply other threads:[~2020-11-01 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 20:04 Alejandro Colomar [this message]
2020-11-02 12:30 ` [PATCH] membarrier.2: Update prototype Mathieu Desnoyers
2020-11-02 16:46 ` Alejandro Colomar
2020-11-02 17:40 ` Peter Oskolkov
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=20201101200440.17328-1-colomar.6.4.3@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=ckennelly@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@google.com \
--cc=posk@posk.io \
--cc=shuah@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