From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Implement the mlock2 function
Date: Fri, 24 Nov 2017 17:09:00 -0000 [thread overview]
Message-ID: <8468ce54-adeb-4560-4323-51908f623bb6@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1711241701280.16849@digraph.polyomino.org.uk>
On 11/24/2017 06:02 PM, Joseph Myers wrote:
> On Fri, 24 Nov 2017, Florian Weimer wrote:
>
>> Fallback using mlock is provided if the flags argument is zero.
>>
>> 2017-11-24 Florian Weimer <fweimer@redhat.com>
>>
>> * sysdeps/unix/sysv/linux/mlock2.c: New file.
>> * sysdeps/unix/sysv/linux/tst-mlock2.c: Likewise.
>> * sysdeps/unix/sysv/linux/Makefile (routines): Add mlock2.
>> (tests): Add tst-mlock2.
>> * sysdeps/unix/sysv/linux/Versions (GLIBC_2.27): Export mlock2.
>> * sysdeps/unix/sysv/linux/libc**.abilist: Update.
>> * manual/memory.texi (Page Lock Functions): Move @end deftypefun
>> for mlock. Document mlock2.
>
> The ChangeLog entry is missing the kernel-features.h change.
>
> The patch is missing a NEWS update.
Thanks, I've fixed those locally.
Florian
next prev parent reply other threads:[~2017-11-24 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 16:59 Florian Weimer
2017-11-24 17:02 ` Joseph Myers
2017-11-24 17:09 ` Florian Weimer [this message]
2017-11-24 17:24 ` Adhemerval Zanella
2017-11-24 19:20 ` Florian Weimer
2017-11-27 13:12 ` Adhemerval Zanella
2017-11-27 16:07 ` Florian Weimer
2017-11-27 16:35 ` Adhemerval Zanella
2017-11-27 16:43 ` Florian Weimer
2017-11-27 18:40 ` Adhemerval Zanella
2017-11-27 18:46 ` Florian Weimer
2017-11-28 13:38 ` Adhemerval Zanella
2017-11-27 9:25 ` Rical Jasan
2017-11-27 10:25 ` Florian Weimer
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=8468ce54-adeb-4560-4323-51908f623bb6@redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).