From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: rppt@kernel.org, mtk.manpages@gmail.com
Cc: akpm@linux-foundation.org, arnd@arndb.de, bp@alien8.de,
catalin.marinas@arm.com, cl@linux.com, dan.j.williams@intel.com,
dave.hansen@linux.intel.com, david@redhat.com,
elena.reshetova@intel.com, hpa@zytor.com, idan.yaniv@ibm.com,
jejb@linux.ibm.com, kirill@shutemov.name,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-man@vger.kernel.org,
linux-mm@kvack.org, linux-nvdimm@lists.01.org,
linux-riscv@lists.infradead.org, luto@kernel.org,
mark.rutland@arm.com, mingo@redhat.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, peterz@infradead.org,
rppt@linux.ibm.com, shuah@kernel.org, tglx@linutronix.de,
tycho@tycho.ws, viro@zeniv.linux.org.uk, will@kernel.org,
willy@infradead.org, x86@kernel.org
Subject: Re: [PATCH] man2: new page describing memfd_secret() system call
Date: Sat, 3 Oct 2020 11:32:43 +0200 [thread overview]
Message-ID: <94cf1b3a-e191-a896-a27d-cd7649cb2c59@gmail.com> (raw)
In-Reply-To: <efb6d051-2104-af26-bfb0-995f4716feb2@gmail.com>
Hi Mike and Michael,
Ping. :)
Thanks,
Alex
On 2020-09-24 16:55, Alejandro Colomar wrote:
> * Mike Rapoport:
> > +.PP
> > +.IR Note :
> > +There is no glibc wrapper for this system call; see NOTES.
>
> You added a reference to NOTES, but then in notes there is nothing about
> it. I guess you wanted to add the following to NOTES (taken from
> membarrier.2):
>
> .PP
> Glibc does not provide a wrapper for this system call; call it using
> .BR syscall (2).
>
> Cheers,
>
> Alex
next prev parent reply other threads:[~2020-10-03 9:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200924132904.1391-1-rppt@kernel.org>
2020-09-24 13:35 ` [PATCH] man2: new page describing memfd_secret() system call Mike Rapoport
2020-09-24 14:55 ` Alejandro Colomar
2020-10-03 9:32 ` Alejandro Colomar [this message]
2020-10-05 7:32 ` Mike Rapoport
2020-11-16 21:01 ` [PATCH v2] memfd_secret.2: New " Alejandro Colomar
2020-11-17 6:26 ` Mike Rapoport
2020-11-21 21:46 ` Alejandro Colomar (man-pages)
2020-11-22 7:03 ` Mike Rapoport
2021-07-27 12:41 [PATCH] man2: new " Mike Rapoport
2021-07-28 20:44 ` Alejandro Colomar (man-pages)
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=94cf1b3a-e191-a896-a27d-cd7649cb2c59@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=elena.reshetova@intel.com \
--cc=hpa@zytor.com \
--cc=idan.yaniv@ibm.com \
--cc=jejb@linux.ibm.com \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.ws \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=x86@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).