From: Peter Oskolkov <posk@google.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Alejandro Colomar <colomar.6.4.3@gmail.com>,
Peter Oskolkov <posk@posk.io>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
paulmck <paulmck@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Turner <pjt@google.com>,
Chris Kennelly <ckennelly@google.com>, shuah <shuah@kernel.org>
Subject: Re: [PATCH] membarrier.2: Update prototype
Date: Mon, 2 Nov 2020 09:40:53 -0800 [thread overview]
Message-ID: <CAPNVh5d-DVLjLg+CBrnPpvSQKE1=cZVAzDhX_eZjoU2+=qhcNw@mail.gmail.com> (raw)
In-Reply-To: <786665141.6911.1604320238880.JavaMail.zimbra@efficios.com>
On Mon, Nov 2, 2020 at 4:30 AM Mathieu Desnoyers
<mathieu.desnoyers@efficios.com> wrote:
>
> ----- On Nov 1, 2020, at 3:04 PM, Alejandro Colomar colomar.6.4.3@gmail.com wrote:
>
> > The Linux kernel now uses 'flags' and added a new argument: 'cpu_id'.
> > These changes were introduced to the kernel
> > in commit 2a36ab717e8fe678d98f81c14a0b124712719840.
>
[...]
> Peter (Oskolkov), can you contribute a patch detailing the new membarrier flags and cpu_id
> arguments to the man pages project ?
Yes, sure, I'll prepare a patch in the next day or two.
Thanks,
Peter
[...]
prev parent reply other threads:[~2020-11-02 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 20:04 [PATCH] membarrier.2: Update prototype Alejandro Colomar
2020-11-02 12:30 ` Mathieu Desnoyers
2020-11-02 16:46 ` Alejandro Colomar
2020-11-02 17:40 ` Peter Oskolkov [this message]
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='CAPNVh5d-DVLjLg+CBrnPpvSQKE1=cZVAzDhX_eZjoU2+=qhcNw@mail.gmail.com' \
--to=posk@google.com \
--cc=boqun.feng@gmail.com \
--cc=ckennelly@google.com \
--cc=colomar.6.4.3@gmail.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@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;
as well as URLs for NNTP newsgroup(s).